call_api

A execute tool on the AWS MCP server.

SERVERAWS SOURCE@awslabs/mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/aws/call-api.md

WHAT IT DOES

What call_api does on AWS

AI agents invoke call_api to trigger actions in AWS. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why call_api is rated High

The name 'call_api' strongly implies executing an API call, which can trigger external operations with side effects. Given the AWS server context and sibling tools that include write/destructive operations (attach_policy, add_user_to_group, etc.), an arbitrary API caller could be highly dangerous. However, the empty description significantly lowers confidence.

From the tool's definition Tool name 'call_api' with empty description; sibling tools suggest AWS operations context

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs call_api safely

PolicyLayer is an MCP gateway: it sits between your AI agents and AWS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For call_api, this is the rule to start with:

call_api Rate-limited

call_api stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "call_api": {
      "limits": [
        {
          "counter": "call_api_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect AWS, apply this rule, and every call_api call is checked against it from then on.

FAQ

Questions about call_api

What does the call_api tool do? +

call_api is a execute tool on the AWS MCP server. 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_api? +

Register the AWS MCP server in PolicyLayer and add a rule for call_api: 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_api? +

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

Can I rate-limit call_api? +

Yes. Add a rate_limit block to the call_api 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_api completely? +

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

call_api 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.

KEEP EXPLORING

More on AWS, and thousands of servers like it.

This server

All 300 AWS tools → High-risk tools on this server →

Across the catalogue

call_rpc on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →