call_api

THE RISK

Low Risk

Why call_api needs a policy

The description is empty and uninformative. The name 'call_api' is generic and could span multiple categories. Given the server context (AWS Pricing MCP Server), it likely reads pricing data, but cannot be certain. Lowering confidence due to lack of evidence. Defaulting to Other given insufficient information, though Read is plausible in context.

From the tool's definition Tool name is 'call_api' with an empty description. No information about what the API call does or its effects.

Documented attack patterns abuse exactly the kind of access call_api gives an agent:

POLICY

How to control call_api

PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Pricing MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for call_api:

policy.json

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

call_api gets a rate cap, and everything else on the server is denied unless you say otherwise.

Create a free account and register AWS Pricing MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

SET A RULE FOR THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More AWS Pricing MCP Server tools

Destructive bulk_delete_by_criteria bulk_delete_by_criteria Destructive cache_delete Delete a value from the cache. Destructive cache_delete_many Delete multiple values from the cache. Destructive cache_delete_multi Delete multiple values from the cache (alias for delete_many). Destructive cancel_logs_insight_query cancel_logs_insight_query Destructive CancelAHORunBatch CancelAHORunBatch Destructive delete delete Destructive delete_access_key delete_access_key

All 805 AWS Pricing MCP Server tools →

Other tools on other servers

Android Forensics ADB MCP Server generate_app_analysis_report Ethereum Tools add Math MCP Server complex_analysis_suite Crypto_MCP aes_encrypt

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Tool risk categories → How PolicyLayer classifies MCP tools by what they can do.
MCP tool → What an MCP tool is and how clients discover and call it.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about call_api

What does the call_api tool do? +

call_api. It is categorised as a Other tool in the AWS Pricing MCP Server MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on call_api? +

Register the AWS Pricing MCP Server 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 Pricing MCP Server. Nothing to install.

What risk level is call_api? +

call_api is a Other tool with low risk. Read-only tools are generally safe to allow by default.

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 Pricing MCP Server MCP server (awslabs.aws-pricing-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every AWS Pricing MCP Server tool call.

Start from AWS Pricing MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →