AI agents invoke call_api_raw to trigger actions in Mcp. 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.
This tool executes arbitrary HTTP requests with full control over method (including POST, PUT, DELETE, PATCH), URL, headers, and body. Depending on the arguments supplied, it could perform reads, writes, deletions, or financial operations. Because the outcome depends entirely on the arguments and spans all categories, Execute is appropriate as it triggers external operations with variable effects.
From the tool's definition Make a raw HTTP request with full control over method, URL construction, headers, query params, body mode, and response parsing.
Attacks that exploit this kind of access
Make a raw HTTP request with full control over method, URL construction, headers, query params, body mode, and response parsing. It is categorised as a Execute tool in the Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP server in PolicyLayer and add a rule for call_api_raw: 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 Mcp. Nothing to install.
call_api_raw is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the call_api_raw 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.
Set action: deny in the PolicyLayer policy for call_api_raw. 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.
call_api_raw is provided by the MCP server (victormyschik/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →