High Risk →

call_aws

Execute authenticated AWS API calls

Risk signalsCan invoke any AWS API

Part of the AWS server.

call_aws can trigger actions in AWS, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE AWS →

Free to start. No card required.

AI agents invoke call_aws to trigger processes or run actions in AWS. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

call_aws can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "call_aws": {
      "limits": [
        {
          "counter": "call_aws_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full AWS policy for all 58 tools.

Get this rule live on your own AWS server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY AWS →

View all 58 tools →

These attack patterns abuse exactly the kind of access call_aws gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so call_aws only ever does what you allow.

SECURE AWS →

Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the call_aws tool do? +

Execute authenticated AWS API calls. It is categorised as a Execute tool in the AWS MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on call_aws? +

Register the AWS MCP server in PolicyLayer and add a rule for call_aws: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches AWS. Nothing to install.

What risk level is call_aws? +

call_aws is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit call_aws? +

Yes. Add a rate_limit block to the call_aws rule in your PolicyLayer 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 call_aws completely? +

Set action: deny in the PolicyLayer policy for call_aws. 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 call_aws? +

call_aws is provided by the AWS MCP server (@awslabs/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every AWS tool call.

Deterministic rules across all 58 AWS tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.