AI agents invoke ml_anomaly_report 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.
The tool runs a computational process (embedding-based anomaly detection) rather than merely retrieving stored data. It triggers ML inference and may query external anonymized trace data. This constitutes an Execute action. Misuse could produce false anomaly signals misleading agent safety controls, giving it medium severity.
From the tool's definition "Run embedding-based anomaly detection on a trace" — actively executes an ML pipeline/computation on data, with optional external community baseline lookup
Attacks that exploit this kind of access
Run embedding-based anomaly detection on a trace, with optional community baseline from shared anonymized traces. 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 ml_anomaly_report: 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.
ml_anomaly_report 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 ml_anomaly_report 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 ml_anomaly_report. 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.
ml_anomaly_report 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 →