Grok Bot: AWS MCP plugin shows connected with 8 tools but every call fails live tool discovery (-32602)

Support Bug Reports
, ,
5

Hey @jsolly, thanks for the report.

The AWS plugin runs a small AWS proxy on your bot’s computer, and that proxy signs requests with whatever AWS sign-in is saved there. When that saved sign-in (IAM Identity Center / SSO, or aws login) has expired, the proxy fails while starting up, and the error that comes back is the generic “Invalid request parameters” you’re seeing. We’re seeing the same pattern from other users of this plugin.

Can you try this in a 1:1 chat with the bot:

  1. Ask the bot to run aws sts get-caller-identity on its computer and show you the full output.
  2. If that mentions an expired token or a failed refresh, ask the bot to run aws sso login --use-device-code (or aws login --remote if that’s how you set it up), then open the link it gives you and finish signing in.
  3. Ask the bot to restart its MCP servers.
  4. Ask it to call aws___list_regions again.

If you never meant to use AWS credentials on that computer, removing the old AWS profile there also works. The plugin then sends unsigned requests, so only the tools that don’t need your AWS account will work.

If step 1 succeeds and the call still fails, reply with what step 1 printed (redact the account number) and the time you retried.