call_endpoint
AI agents invoke call_endpoint to trigger actions in Mcp Camara. 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 name 'call_endpoint' strongly suggests executing API calls, potentially to arbitrary endpoints. Without a description, we cannot confirm read-only vs. write behavior. Given sibling tools already handle specific read operations (get_bills_by_deputy, get_deputy_by_name, etc.), this tool likely serves as a generic executor for any API endpoint, which could trigger non-read operations.
From the tool's definition Tool name 'call_endpoint' with empty description. The name implies executing an HTTP call to an arbitrary API endpoint.
Attacks that exploit this kind of access
call_endpoint. It is categorised as a Execute tool in the Mcp Camara MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Camara 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 Camara. 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 Camara MCP server (vrtornisiello/mcp-camara). 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 →