Synthesis — what is notable in YOUR sky right now (lat/lon): the live almanac (sun, moon phase, planets above your horizon), near-Earth asteroid close approaches this week, and the ISS (position + whether it is above your horizon now). One call, three sources, per-section found/error.
AI agents call space.skywatch 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 synthesizes publicly available astronomical and space observation data based on geographic coordinates. It performs no writes, deletions, code execution, or financial operations. The three data sources mentioned (almanac data, asteroid tracking, ISS position) are all read-only queries.
From the tool's definition Tool description explicitly states it provides 'live almanac (sun, moon phase, planets above your horizon), near-Earth asteroid close approaches this week, and the ISS (position + whether it is above your horizon now)' — all retrieval operations with no…
Attacks that exploit this kind of access
Synthesis — what is notable in YOUR sky right now (lat/lon): the live almanac (sun, moon phase, planets above your horizon), near-Earth asteroid close approaches this week, and the ISS (position + whether it is above your horizon now). One call, three sources, per-section found/error. 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.skywatch: 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.skywatch 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.skywatch 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.skywatch. 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.skywatch 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 →