Medium Risk

CreateTokenWithIAM

Get a token using the authorization code through IAM. This tool calls the CreateTokenWithIAM API to get a token using the authorization code received from the OIDC endpoint. Parameters: idc_application_arn (str): The Amazon Q Business application ID redirect_uri (str): The redirect URL ...

Accepts freeform code/query input (code)

Part of the AWS Labs amazon-qindex MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use CreateTokenWithIAM to create or modify resources in AWS Labs amazon-qindex MCP Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call CreateTokenWithIAM repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach AWS Labs amazon-qindex MCP Server.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

aws-labs-amazon-qindex-mcp-server.yaml
tools:
  CreateTokenWithIAM:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full AWS Labs amazon-qindex MCP Server policy for all 4 tools.

Tool Name CreateTokenWithIAM
Category Write
Risk Level Medium

Agents calling write-class tools like CreateTokenWithIAM have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the CreateTokenWithIAM tool do? +

Get a token using the authorization code through IAM. This tool calls the CreateTokenWithIAM API to get a token using the authorization code received from the OIDC endpoint. Parameters: idc_application_arn (str): The Amazon Q Business application ID redirect_uri (str): The redirect URL registered during ISV registration code (str): The authorization code received from OIDC endpoint idc_region (str): The AWS region for IAM Identity Center role_arn (str): The ARN of the IAM role to assume Returns: Dict: Response containing the token information { 'accessToken': 'string', 'tokenType': 'string', 'expiresIn': 123, 'refreshToken': 'string', 'idToken': 'string' }. It is categorised as a Write tool in the AWS Labs amazon-qindex MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on CreateTokenWithIAM? +

Add a rule in your Intercept YAML policy under the tools section for CreateTokenWithIAM. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS Labs amazon-qindex MCP Server MCP server.

What risk level is CreateTokenWithIAM? +

CreateTokenWithIAM is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit CreateTokenWithIAM? +

Yes. Add a rate_limit block to the CreateTokenWithIAM rule in your Intercept policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block CreateTokenWithIAM completely? +

Set action: deny in the Intercept policy for CreateTokenWithIAM. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides CreateTokenWithIAM? +

CreateTokenWithIAM is provided by the AWS Labs amazon-qindex MCP Server MCP server (awslabs.amazon-qindex-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.