AI agents call get_app_ratings 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 historical app ratings from the ASO database. It performs no modifications, deletions, code execution, or financial operations. The 'get' verb and context of querying performance metrics classify it as a Read operation with low severity, as misuse would only expose existing data without side effects.
From the tool's definition Tool name 'get_app_ratings' and description 'Get app rating history' indicate data retrieval without modification. The verb 'get' and the read-only nature of accessing historical rating data confirm this is a query operation.
Documented attack patterns abuse exactly the kind of access get_app_ratings 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 get_app_ratings:
{
"version": "1",
"default": "deny",
"tools": {
"get_app_ratings": {}
}
}get_app_ratings 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.
Get app rating history. 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 get_app_ratings: 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.
get_app_ratings 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 get_app_ratings 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 get_app_ratings. 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.
get_app_ratings 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.