geopass_status
Fetch the stored in-session GEOPass report and geopass_receipt_v1 envelope for a run started through geopass_run.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/geopass-status.md
What geopass_status does on UnClick
AI agents call geopass_status 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 |
|---|---|---|---|
run_id | string | Yes | The GEOPass run id returned by geopass_run |
Parameters from the server's own tool schema.
Why geopass_status is rated Low
This tool queries and retrieves session data (a GEOPass report and receipt envelope) without modifying, deleting, or executing operations. Fetching stored reports is a read-only action with minimal blast radius — the worst case is information disclosure of data already generated in a prior session.
From the tool's definition Tool description states 'Fetch the stored in-session GEOPass report' — fetch is a retrieval operation with no side effects. It retrieves previously stored data from a run that was initiated separately via geopass_run.
Attacks that exploit this kind of access
The rule that runs geopass_status 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 geopass_status, this is the rule to start with:
geopass_status 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 geopass_status call is checked against it from then on.
Questions about geopass_status
Fetch the stored in-session GEOPass report and geopass_receipt_v1 envelope for a run started through geopass_run. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
geopass_status accepts 1 parameter: run_id. Required: run_id. 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 geopass_status: 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.
geopass_status 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 geopass_status 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 geopass_status. 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.
geopass_status 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