space.satellites

Search the catalog of ~69k cataloged Earth-orbiting objects (CelesTrak SATCAT). Filter by name (q, e.g.

SERVERMcp SOURCE@2sio/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-2s-io-mcp/space.satellites.md

WHAT IT DOES

What space.satellites does on Mcp

AI agents call space.satellites to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why space.satellites is rated Low

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

RECOMMENDED RULE

The rule that runs space.satellites safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For space.satellites, this is the rule to start with:

space.satellites Allowed

space.satellites is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "space.satellites": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every space.satellites call is checked against it from then on.

FAQ

Questions about space.satellites

What does the space.satellites tool do? +

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.

How do I enforce a policy on space.satellites? +

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.

What risk level is space.satellites? +

space.satellites is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit space.satellites? +

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.

How do I block space.satellites completely? +

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.

What MCP server provides space.satellites? +

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.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 572 tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →