Get the current location of the International Space Station.
AI agents call get_iss_location to retrieve information from Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves real-time positional data about the ISS from a public data source. It performs no modifications, deletions, code execution, or financial transactions. It is a straightforward read operation with no blast radius if misused—an AI agent calling this repeatedly or with incorrect parameters would simply receive location data with no harm to any system.
From the tool's definition Tool name 'get_iss_location' and description 'Get the current location of the International Space Station' indicate a retrieval operation with no side effects. This is a pure query of public ISS tracking data.
Attacks that exploit this kind of access
Get the current location of the International Space Station. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Integrations MCP server in PolicyLayer and add a rule for get_iss_location: 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 Integrations MCP. Nothing to install.
get_iss_location 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 get_iss_location 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 get_iss_location. 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.
get_iss_location is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). 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 →