satellite_passes
skypeek: Predict satellite passes over a location. For sun and moon times use sun_moon_times. Returns the passes of a satellite (default the ISS) over a point in the next 1-3 days: start, highest and end times with azimuth and elevation, duration, and whether the pass is visible to the eye. SGP4 ...
This record as markdown: /tools/dev-tanod-tanod/satellite-passes.md
What satellite_passes does on Tanod
AI agents invoke satellite_passes to trigger actions in Tanod. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
lat | number | Yes | Latitude in degrees (-90 to 90). |
lon | number | Yes | Longitude in degrees (-180 to 180). |
days | integer | — | Window in days (1-3). |
alt_m | number | — | Observer altitude in metres. |
norad_id | integer | — | NORAD catalog number (default 25544, the ISS); CelesTrak 'stations' and 'visual' groups plus NOAA 15 / 18 / 19. |
visible_only | boolean | — | Only passes that can be seen with the eye (satellite sunlit, sky dark). |
min_elevation | number | — | Lowest elevation counted as a pass, in degrees above the horizon. |
Parameters from the server's own tool schema.
Why satellite_passes is rated High
satellite_passes triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs satellite_passes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For satellite_passes, this is the rule to start with:
satellite_passes stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tanod, apply this rule, and every satellite_passes call is checked against it from then on.
Questions about satellite_passes
skypeek: Predict satellite passes over a location. For sun and moon times use sun_moon_times. Returns the passes of a satellite (default the ISS) over a point in the next 1-3 days: start, highest and end times with azimuth and elevation, duration, and whether the pass is visible to the eye. SGP4 predictions, not observations, from CelesTrak orbital elements (only derived pass times are returned; no endorsement by CelesTrak implied). Satellites: CelesTrak's 'stations' and 'visual' groups plus NOAA 15 / 18 / 19; another NORAD id is a 422 (not charged). At most 40 passes. A cold orbital-data cache or an upstream outage can be a 503 (not charged; retry). Typically under 1 s; with a cold orbital-data cache up to a minute or more (a 503 when too slow, not charged: retry). Price: USD 0.002. Free: 5 skypeek calls per IP per UTC day. Docs: https://tanod.dev/learn/iss-pass-times-api.html. It is categorised as a Execute tool in the Tanod MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
satellite_passes accepts 7 parameters: lat, lon, days, alt_m, norad_id, visible_only, min_elevation. Required: lat, lon. The full parameter table on this page comes from the server's own tool schema.
Register the Tanod MCP server in PolicyLayer and add a rule for satellite_passes: 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 Tanod. Nothing to install.
satellite_passes is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the satellite_passes 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 satellite_passes. 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.
satellite_passes is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tanod, and thousands of servers like it.
Across the catalogue