AI agents invoke maple_autoroute_call to trigger actions in Maple. 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 downstream tools on behalf of an LLM agent — it resolves, connects, and invokes tools through a firewall in a single call. The blast radius is critical because it acts as a universal execution gateway: a misuse or prompt injection could trigger any downstream tool (including destructive or financial ones) through this single entry point.
From the tool's definition 'One-call execution path for LLMs: resolve downstream app, optionally auto-connect from marketplace, then call the requested tool through Maple firewall.'
Attacks that exploit this kind of access
One-call execution path for LLMs: resolve downstream app, optionally auto-connect from marketplace, then call the requested tool through Maple firewall. It is categorised as a Execute tool in the Maple MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Maple MCP server in PolicyLayer and add a rule for maple_autoroute_call: 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 Maple. Nothing to install.
maple_autoroute_call 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 maple_autoroute_call 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 maple_autoroute_call. 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.
maple_autoroute_call is provided by the Maple MCP server (omar2001ramadan/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 →