space.launches
Upcoming or recent orbital rocket launches (Launch Library 2). when=upcoming|previous, optional search by rocket/provider/mission. Returns name, status, launch time + window, provider, rocket, pad, mission, webcast.
This record as markdown: /tools/io-github-2s-io-mcp/space.launches.md
What space.launches does on Mcp
AI agents call space.launches 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.
Why space.launches is rated Low
This tool retrieves publicly available information about rocket launches from Launch Library 2. It has no side effects—it only queries and returns data without creating, modifying, deleting, or executing any operations. The optional search parameters (when, rocket, provider, mission) are filter arguments for data retrieval, not actions.
From the tool's definition Tool description states it returns data about "Upcoming or recent orbital rocket launches" with fields like name, status, launch time, provider, rocket, pad, mission, webcast. The verbs are 'Returns' (retrieval) and optional 'search' (query).
Attacks that exploit this kind of access
The rule that runs space.launches 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.launches, this is the rule to start with:
space.launches is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every space.launches call is checked against it from then on.
Questions about space.launches
Upcoming or recent orbital rocket launches (Launch Library 2). when=upcoming|previous, optional search by rocket/provider/mission. Returns name, status, launch time + window, provider, rocket, pad, mission, webcast. 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.launches: 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.launches 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.launches 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.launches. 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.launches 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.
More on , and thousands of servers like it.
This server
Across the catalogue