celestrak.satellite.intdes
Look up satellite orbital elements using the international designator (COSPAR ID / Harvard designation). Returns orbital element sets for all objects associated with the designator: primary payload (suffix A), rocket body (B), and debris fragments (C onward). Format is YYYY-NNNX where YYYY=launch...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/celestrak.satellite.intdes.md
What celestrak.satellite.intdes does on Apibase
AI agents call celestrak.satellite.intdes 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 |
|---|---|---|---|
intdes | string | Yes | International designator (COSPAR ID) for the launch or object. Format: YYYY-NNNX where YYYY is launch year, NNN is launch number of that year (3 digits), and X |
Parameters from the server's own tool schema.
Why celestrak.satellite.intdes is rated Low
Tool retrieves publicly available satellite orbital data without modification or side effects.
From the tool's definition Look up satellite orbital elements, returns orbital element sets, query operation.
Attacks that exploit this kind of access
The rule that runs celestrak.satellite.intdes 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 celestrak.satellite.intdes, this is the rule to start with:
celestrak.satellite.intdes 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 celestrak.satellite.intdes call is checked against it from then on.
Questions about celestrak.satellite.intdes
Look up satellite orbital elements using the international designator (COSPAR ID / Harvard designation). Returns orbital element sets for all objects associated with the designator: primary payload (suffix A), rocket body (B), and debris fragments (C onward). Format is YYYY-NNNX where YYYY=launch year, NNN=launch number of year (zero-padded to 3 digits), X=piece letter. Examples: "1998-067A" (ISS ZARYA module launched 1998, 67th launch, primary payload), "1990-037B" (Hubble Space Telescope), "2019-029B" (Starlink batch 1 rocket body). Useful when you know the mission designator but not the NORAD catalog number. Data from US Space Force via CelesTrak. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
celestrak.satellite.intdes accepts 1 parameter: intdes. Required: intdes. 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 celestrak.satellite.intdes: 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.
celestrak.satellite.intdes 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 celestrak.satellite.intdes 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 celestrak.satellite.intdes. 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.
celestrak.satellite.intdes 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