AI agents call compare_rankings to retrieve information from Astro MCP Server 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 ranking data between two points in time. It has no side effects, does not modify data, execute code, or trigger external operations. It is purely a data retrieval and comparison function, fitting the Read category. The low severity reflects minimal blast radius—misuse would only expose or analyze existing ASO data without enabling harmful downstream actions.
From the tool's definition Tool name 'compare_rankings' and description 'Compare keyword rankings between two dates' indicate a query/retrieval operation. No modification, deletion, or execution of external processes.
Documented attack patterns abuse exactly the kind of access compare_rankings gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Astro MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for compare_rankings:
{
"version": "1",
"default": "deny",
"tools": {
"compare_rankings": {}
}
}compare_rankings 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.
Compare keyword rankings between two dates. It is categorised as a Read tool in the Astro MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Astro MCP Server MCP server in PolicyLayer and add a rule for compare_rankings: 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 Astro MCP Server. Nothing to install.
compare_rankings 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 compare_rankings 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 compare_rankings. 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.
compare_rankings is provided by the Astro MCP Server MCP server (timbroddin/astro-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Astro MCP Server, 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.
15 Astro MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.