Year-over-year comparison for any metric.
AI agents call yoy_comparison to retrieve information from AdminAgent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and compares historical metric data across time periods. It is a read/analytics operation with no side effects — it queries existing store data to produce a comparison report. No data is created, modified, deleted, or financially transacted.
From the tool's definition Year-over-year comparison for any metric
Attacks that exploit this kind of access
Year-over-year comparison for any metric. It is categorised as a Read tool in the AdminAgent MCP Server, which means it retrieves data without modifying state.
Register the AdminAgent MCP server in PolicyLayer and add a rule for yoy_comparison: 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 AdminAgent. Nothing to install.
yoy_comparison 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 yoy_comparison 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 yoy_comparison. 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.
yoy_comparison is provided by the AdminAgent MCP server (rushikeshmore/admin-agent). 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 →