Call an endpoint discovered from the OpenAPI document, optionally applying auth automatically and sending query, path, headers, and payload data.
AI agents invoke call_endpoint to trigger actions in MCP OpenAPI Discovery. 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 real HTTP requests against external APIs, potentially performing any operation (read, write, delete, financial) depending on the endpoint called. Since the effect is entirely argument-dependent and can span all severity levels, Execute is the correct category. The blast radius is high because an AI agent could call destructive or financial endpoints with attacker-controlled parameters.
From the tool's definition 'Call an endpoint discovered from the OpenAPI document... sending query, path, headers, and payload data' — triggers external HTTP requests with arbitrary parameters, auth, and payloads
Attacks that exploit this kind of access
Call an endpoint discovered from the OpenAPI document, optionally applying auth automatically and sending query, path, headers, and payload data. It is categorised as a Execute tool in the MCP OpenAPI Discovery MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP OpenAPI Discovery MCP server in PolicyLayer and add a rule for call_endpoint: 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 OpenAPI Discovery. Nothing to install.
call_endpoint 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_endpoint 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_endpoint. 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_endpoint is provided by the MCP OpenAPI Discovery MCP server (rekl0w/mcp-openapi-discovery). 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 →