AI agents call space.satellites to retrieve information from Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing satellite catalog data from CelesTrak SATCAT without modifying, deleting, or executing operations. The search and filter capabilities are characteristic of Read operations. Low severity because access to public satellite catalog information poses minimal risk even if misused by an agent.
From the tool's definition Tool description explicitly states 'Search the catalog' of satellite data and mentions filtering by name (q parameter), indicating a query/search operation with no side effects.
Attacks that exploit this kind of access
Search the catalog of ~69k cataloged Earth-orbiting objects (CelesTrak SATCAT). Filter by name (q, e.g. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for space.satellites: 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 Mcp. Nothing to install.
space.satellites 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 space.satellites 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 space.satellites. 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.
space.satellites is provided by the MCP server (@2sio/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 →