Detect anomalies for one campaign by comparing its current
AI agents call analysis_anomalies_check to retrieve information from Mureo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs anomaly detection by comparing campaign metrics. It retrieves and analyzes data to identify deviations but does not modify, execute commands, delete, or move money. It falls squarely into the Read category as a diagnostic query with no side effects. Severity is low because even if an agent misuses it, the worst outcome is incorrect anomaly reports without financial or data integrity consequences.
From the tool's definition Tool name 'analysis_anomalies_check' and description 'Detect anomalies for one campaign by comparing its current' indicate a comparative analysis operation. The verb 'detect' and 'check' are diagnostic/analytical in nature.
Documented attack patterns abuse exactly the kind of access analysis_anomalies_check gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mureo, and nothing reaches the server without passing your rules. This is the rule we recommend for analysis_anomalies_check:
{
"version": "1",
"default": "deny",
"tools": {
"analysis_anomalies_check": {}
}
}analysis_anomalies_check is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Detect anomalies for one campaign by comparing its current. It is categorised as a Read tool in the Mureo MCP Server, which means it retrieves data without modifying state.
Register the Mureo MCP server in PolicyLayer and add a rule for analysis_anomalies_check: 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 Mureo. Nothing to install.
analysis_anomalies_check is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the analysis_anomalies_check 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 analysis_anomalies_check. 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.
analysis_anomalies_check is provided by the Mureo MCP server (logly/mureo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mureo, 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.
185 Mureo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.