Flag days with unusual revenue or impression changes vs rolling average. Use for:
AI agents call anomaly_detection to retrieve information from AdMob MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
anomaly_detection retrieves and analyzes ad revenue data to detect statistical outliers, returning insights to the user. It has no side effects—it does not create, modify, delete data, execute code, trigger external operations, or commit financial transactions. This is purely a Read operation within the analytical/monitoring domain.
From the tool's definition Tool description states 'Flag days with unusual revenue or impression changes vs rolling average' — this is a querying/analysis operation that identifies anomalies in historical data without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Flag days with unusual revenue or impression changes vs rolling average. Use for:. It is categorised as a Read tool in the AdMob MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AdMob MCP Server MCP server in PolicyLayer and add a rule for anomaly_detection: 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 AdMob MCP Server. Nothing to install.
anomaly_detection 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 anomaly_detection 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 anomaly_detection. 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.
anomaly_detection is provided by the AdMob MCP Server MCP server (willhou/admob-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
anomaly_detection is one line of AdMob MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →