AI agents call search_astroquery_services 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 tool retrieves metadata about available astronomical databases and services based on search criteria. It does not execute queries against those databases, modify data, or trigger external operations. It is purely informational and read-only in nature, making it a low-risk Read category tool.
From the tool's definition search_astroquery_services" is described as enabling users to "Search astroquery services by data type, wavelength coverage, object type, or other criteria" - a query and discovery function with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Search astroquery services by data type, wavelength coverage, object type, or other criteria. 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 search_astroquery_services: 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.
search_astroquery_services 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 search_astroquery_services 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 search_astroquery_services. 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.
search_astroquery_services 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 →