iss_flyover
Get upcoming ISS flyover times for a location (lat/lon).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/iss-flyover.md
What iss_flyover does on UnClick
AI agents call iss_flyover to retrieve information from UnClick 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 |
|---|---|---|---|
lat | number | Yes | Latitude. |
lon | number | Yes | Longitude. |
count | number | — | Number of flyovers (max 20, default 5). |
Parameters from the server's own tool schema.
Why iss_flyover is rated Low
This tool retrieves and returns ISS flyover schedule data based on latitude/longitude coordinates provided by the user. It performs a lookup or query of existing public data without creating, modifying, deleting, or executing any operations. The only risk is information disclosure, which is minimal given ISS data is publicly available.
From the tool's definition Tool name 'iss_flyover' and description 'Get upcoming ISS flyover times for a location (lat/lon)' indicate a query operation that retrieves astronomical data.
Attacks that exploit this kind of access
The rule that runs iss_flyover safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For iss_flyover, this is the rule to start with:
iss_flyover 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 UnClick, apply this rule, and every iss_flyover call is checked against it from then on.
Questions about iss_flyover
Get upcoming ISS flyover times for a location (lat/lon). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
iss_flyover accepts 3 parameters: lat, lon, count. Required: lat, lon. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for iss_flyover: 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 UnClick. Nothing to install.
iss_flyover 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 iss_flyover 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 iss_flyover. 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.
iss_flyover is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue