launch-library-2.launches.detail
Get full detail for a single launch by its UUID (from launch-library-2.upcoming_launches results) — mission description, orbit, rocket and pad detail, launch provider, imagery, and probability/weather notes. Data: ll.thespacedevs.com (The Space Devs), no auth required; free tier is throttled to 1...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/launch-library-2.launches.detail.md
What launch-library-2.launches.detail does on Apibase
AI agents call launch-library-2.launches.detail to retrieve information from Apibase 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 |
|---|---|---|---|
id | string | Yes | Launch UUID from launch-library-2.upcoming_launches results, e.g. "521f3a1c-f977-4306-9b7f-495858719adf" |
Parameters from the server's own tool schema.
Why launch-library-2.launches.detail is rated Low
Retrieves read-only launch data with no side effects or modifications.
From the tool's definition Get full detail for a single launch by its UUID
Attacks that exploit this kind of access
The rule that runs launch-library-2.launches.detail safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For launch-library-2.launches.detail, this is the rule to start with:
launch-library-2.launches.detail 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 Apibase, apply this rule, and every launch-library-2.launches.detail call is checked against it from then on.
Questions about launch-library-2.launches.detail
Get full detail for a single launch by its UUID (from launch-library-2.upcoming_launches results) — mission description, orbit, rocket and pad detail, launch provider, imagery, and probability/weather notes. Data: ll.thespacedevs.com (The Space Devs), no auth required; free tier is throttled to 15 requests/hour shared across all APIbase agents, so results are cached for 1 hour. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
launch-library-2.launches.detail accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for launch-library-2.launches.detail: 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 Apibase. Nothing to install.
launch-library-2.launches.detail 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 launch-library-2.launches.detail 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 launch-library-2.launches.detail. 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.
launch-library-2.launches.detail is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue