celestrak.satellite.search
Search the NORAD satellite catalog by name substring (case-insensitive). Returns all satellites whose name contains the query string, each with NORAD catalog number, international designator (COSPAR ID), epoch, and full orbital element set. Useful for finding the NORAD IDs and TLEs of satellites ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/celestrak.satellite.search.md
What celestrak.satellite.search does on Apibase
AI agents use celestrak.satellite.search to create or update resources in Apibase, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apibase environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Satellite name substring to search (case-insensitive). Examples: "ISS", "STARLINK", "GPS", "NOAA", "GOES", "HUBBLE", "FENGYUN". Returns all satellites whose nam |
Parameters from the server's own tool schema.
Why celestrak.satellite.search is rated Medium
An AI agent can call celestrak.satellite.search faster than any human can review: one bad instruction and it creates or modifies resources in Apibase by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs celestrak.satellite.search 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.search, this is the rule to start with:
celestrak.satellite.search stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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.search call is checked against it from then on.
Questions about celestrak.satellite.search
Search the NORAD satellite catalog by name substring (case-insensitive). Returns all satellites whose name contains the query string, each with NORAD catalog number, international designator (COSPAR ID), epoch, and full orbital element set. Useful for finding the NORAD IDs and TLEs of satellites by operator or mission name (e.g. "STARLINK" returns all ~6000 Starlink satellites, "NOAA" returns NOAA weather sats, "GPS" returns GPS block satellites, "FENGYUN" returns Chinese weather satellites, "ISS" returns ISS modules). Data from US Space Force via CelesTrak, no auth required. It is categorised as a Write tool in the Apibase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
celestrak.satellite.search accepts 1 parameter: name. Required: name. 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.search: 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.search is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the celestrak.satellite.search 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.search. 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.search 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