iss_location
Get the current location of the International Space Station.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/iss-location.md
What iss_location does on UnClick
AI agents call iss_location 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.
Why iss_location is rated Low
This tool performs a simple data retrieval—fetching the current coordinates/position of a publicly tracked object (the ISS). There is no modification, deletion, execution of code, or financial transaction involved. It is a straightforward Read operation with minimal security risk.
From the tool's definition Tool name 'iss_location' and description 'Get the current location of the International Space Station' indicate a query operation that retrieves real-time orbital data.
Attacks that exploit this kind of access
The rule that runs iss_location 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_location, this is the rule to start with:
iss_location 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_location call is checked against it from then on.
Questions about iss_location
Get the current location of the International Space Station. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
Register the UnClick MCP server in PolicyLayer and add a rule for 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 UnClick. Nothing to install.
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 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 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.
iss_location 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