AI agents call space.system 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 queries a database of exoplanetary systems and returns profile information based on stellar name input. It is a read-only retrieval operation with no side effects, no code execution, and no data modification. The pay-per-call model on 2s.io does not change the functional category — the tool itself performs a benign data query.
From the tool's definition Tool description indicates 'profile a confirmed exoplanetary system by host-star name' — a lookup/query operation that retrieves astronomical data without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Synthesis — profile a confirmed exoplanetary system by host-star name (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.system: 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.system 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.system 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.system. 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.system 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 →