Get satellite orbital elements (TLE / GP data) for a single object by NORAD catalog ID. Returns orbital parameters: inclination, eccentricity, mean motion, RAAN, argument of perigee, epoch, and derived orbital period in minutes. norad_id 25544 = ISS, 20580 = Hubble. This is the orbital catalog, n...
AI agents call get_satellite to retrieve information from Mcp Celestrak without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
norad_id | number | Yes | NORAD catalog ID, e.g. 25544 (ISS) or 20580 (Hubble). |
Parameters from the server's own tool schema.
This tool performs a simple query of publicly available orbital catalog data. It returns static orbital parameters for satellites identified by NORAD catalog ID. There are no side effects, no data modification, no code execution, and no destructive or financial operations. The data retrieved (TLE/orbital elements) is non-sensitive public information used for astronomy and satellite tracking.
From the tool's definition Tool retrieves satellite orbital elements (TLE / GP data) and returns orbital parameters including inclination, eccentricity, mean motion, epoch, and orbital period.
Attacks that exploit this kind of access
Get satellite orbital elements (TLE / GP data) for a single object by NORAD catalog ID. Returns orbital parameters: inclination, eccentricity, mean motion, RAAN, argument of perigee, epoch, and derived orbital period in minutes. norad_id 25544 = ISS, 20580 = Hubble. This is the orbital catalog, not live position tracking. It is categorised as a Read tool in the Mcp Celestrak MCP Server, which means it retrieves data without modifying state.
get_satellite accepts 1 parameter: norad_id. Required: norad_id. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Celestrak MCP server in PolicyLayer and add a rule for get_satellite: 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 Celestrak. Nothing to install.
get_satellite 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_satellite 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_satellite. 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_satellite is provided by the Mcp Celestrak MCP server (pipeworx-io/mcp-celestrak). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →