# 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.

Agent View of the PolicyLayer registry record for `get_next_launches`. HTML page: https://policylayer.com/tools/com-gocosmik-cosmik/get-next-launches

## Facts

- Tool: `get_next_launches`
- Server: Cosmik (`https://gocosmik.com/api/mcp`) — https://policylayer.com/tools/com-gocosmik-cosmik.md
- Homepage: https://github.com/crashedfox/cosmik-mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 2
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `limit` | integer | no | Maximum number of launches to return (1-20, default 5) |
| `provider` | string | no | Case-insensitive filter matched against provider and rocket name, e.g. 'SpaceX', 'NASA', 'Rocket Lab' |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_next_launches",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Cosmik:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_next_launches": {}
  }
}
```

## Other tools on Cosmik (2)

- `get_iss_passes` — Read — https://policylayer.com/tools/com-gocosmik-cosmik/get-iss-passes.md
- `get_launch_news` — Read — https://policylayer.com/tools/com-gocosmik-cosmik/get-launch-news.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-gocosmik-cosmik · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-gocosmik-cosmik