get_next_launches
Live schedule of upcoming orbital rocket launches (SpaceX, NASA, Rocket Lab, ULA, Arianespace, China…) with liftoff times (UTC), pads, status and a live-tracking link. Optionally filter by provider/rocket name.
This record as markdown: /tools/com-gocosmik-cosmik/get-next-launches.md
What get_next_launches does on Cosmik
AI agents call get_next_launches to retrieve information from Cosmik without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Maximum number of launches to return (1-20, default 5) |
provider | string | — | Case-insensitive filter matched against provider and rocket name, e.g. 'SpaceX', 'NASA', 'Rocket Lab' |
Parameters from the server's own tool schema.
Why get_next_launches is rated Low
This tool performs data retrieval only—it queries and returns publicly available space launch information without side effects. No data is created, modified, deleted, or executed. The optional filtering parameter is a standard read-operation feature. The low severity reflects minimal blast radius if misused by an AI agent, as it can only access or display launch schedule information.
From the tool's definition Tool retrieves 'live schedule of upcoming orbital rocket launches' with 'liftoff times, pads, status and a live-tracking link' and allows optional filtering. All operations are informational queries with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs get_next_launches safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cosmik, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_next_launches, this is the rule to start with:
get_next_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 Cosmik, apply this rule, and every get_next_launches call is checked against it from then on.
Questions about get_next_launches
Live schedule of upcoming orbital rocket launches (SpaceX, NASA, Rocket Lab, ULA, Arianespace, China…) with liftoff times (UTC), pads, status and a live-tracking link. Optionally filter by provider/rocket name. It is categorised as a Read tool in the Cosmik MCP Server, which means it retrieves data without modifying state.
get_next_launches accepts 2 parameters: limit, provider. The full parameter table on this page comes from the server's own tool schema.
Register the Cosmik MCP server in PolicyLayer and add a rule for get_next_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 Cosmik. Nothing to install.
get_next_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 get_next_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 get_next_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.
get_next_launches is provided by the Cosmik MCP server (https://gocosmik.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cosmik, and thousands of servers like it.
This server
Across the catalogue