iss.space.position
Get the real-time position of the International Space Station — latitude, longitude, altitude (km), velocity (km/h), and daylight/eclipse visibility. ISS orbits at 28,000 km/h, completes one orbit every 90 minutes. Updates every ~60 seconds.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/iss.space.position.md
What iss.space.position does on Apibase
AI agents call iss.space.position to retrieve information from Apibase 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 |
|---|---|---|---|
units | string | — | Distance units: kilometers (default) or miles |
Parameters from the server's own tool schema.
Why iss.space.position is rated Low
Tool retrieves public ISS telemetry data with no side effects or ability to modify systems.
From the tool's definition Get the real-time position of the International Space Station — latitude, longitude, altitude
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs iss.space.position 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 iss.space.position, this is the rule to start with:
iss.space.position 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 Apibase, apply this rule, and every iss.space.position call is checked against it from then on.
Questions about iss.space.position
Get the real-time position of the International Space Station — latitude, longitude, altitude (km), velocity (km/h), and daylight/eclipse visibility. ISS orbits at 28,000 km/h, completes one orbit every 90 minutes. Updates every ~60 seconds. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
iss.space.position accepts 1 parameter: units. 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 iss.space.position: 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.
iss.space.position 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.space.position 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.space.position. 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.space.position 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