AI agents call get_astroquery_service_details to retrieve information from Astro MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a metadata/introspection tool that returns service documentation and capabilities. It performs no data extraction, modification, deletion, or external operations. The user is simply querying the schema and available options of an astronomical database service, which is a read-only operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool retrieves and displays 'detailed information' about astroquery services including 'capabilities, data types, and example queries'—purely informational with no side effects or modifications.
Attacks that exploit this kind of access
Get detailed information about a specific astroquery service including capabilities, data types, and example queries. It is categorised as a Read tool in the Astro MCP MCP Server, which means it retrieves data without modifying state.
Register the Astro MCP server in PolicyLayer and add a rule for get_astroquery_service_details: 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. Nothing to install.
get_astroquery_service_details 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_astroquery_service_details 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_astroquery_service_details. 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_astroquery_service_details is provided by the Astro MCP server (sandyyuan/astro_mcp). 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 →