Search the satellite catalog by name substring and return matching orbital elements (TLE / GP data). e.g. "STARLINK", "NOAA", "GPS". Returns up to 50 matches with orbital parameters (inclination, eccentricity, period). Catalog/orbital data, not live tracking.
AI agents call search_by_name 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 |
|---|---|---|---|
name | string | Yes | Satellite name substring, e.g. "STARLINK" or "NOAA". |
Parameters from the server's own tool schema.
This tool is a query/search function that retrieves public satellite orbital data. It does not create, modify, delete, execute code, or involve financial transactions. The returned TLE (Two-Line Element) and GP (General Perturbations) data are standard, publicly available orbital elements used in astronomy and satellite tracking.
From the tool's definition The tool 'Search the satellite catalog by name substring and return matching orbital elements (TLE / GP data).' Performs a search operation that retrieves and returns orbital data without modification.
Attacks that exploit this kind of access
Search the satellite catalog by name substring and return matching orbital elements (TLE / GP data). e.g. "STARLINK", "NOAA", "GPS". Returns up to 50 matches with orbital parameters (inclination, eccentricity, period). Catalog/orbital data, not live tracking. It is categorised as a Read tool in the Mcp Celestrak MCP Server, which means it retrieves data without modifying state.
search_by_name accepts 1 parameter: name. Required: name. 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 search_by_name: 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.
search_by_name 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 search_by_name 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 search_by_name. 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.
search_by_name 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 →