AI agents invoke call_api to trigger actions in Prometheus MCP Server. 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.
The tool name 'call_api' suggests it executes API calls, likely against AWS Managed Prometheus. API calls can have a wide range of effects (read, write, or destructive), but without a description, the most cautious defensible category for an arbitrary API caller is Execute. Confidence is lowered due to the empty description providing no further detail on what the API call does or what parameters it accepts.
From the tool's definition Tool name 'call_api' with empty description — name implies invoking an API endpoint, which is an external operation.
Documented attack patterns abuse exactly the kind of access call_api gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Prometheus MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for call_api:
{
"version": "1",
"default": "deny",
"tools": {
"call_api": {
"limits": [
{
"counter": "call_api_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
call_api. It is categorised as a Execute tool in the Prometheus MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Prometheus 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 Prometheus MCP Server. Nothing to install.
call_api 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 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. 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 is provided by the Prometheus MCP Server MCP server (awslabs.prometheus-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Prometheus MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
805 Prometheus MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.