geopass_run

SERVERUnClick SOURCE@unclick/mcp-server

High RISK CLASS

Category Execute

Parameters 40 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/geopass-run.md

WHAT IT DOES

What geopass_run does on UnClick

AI agents invoke geopass_run to trigger actions in UnClick. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`url`	string	—	Target public http(s) URL for a one-off GEOPass read-only run
`checks`	array	—	Optional GEOPass check ids. Defaults to the public-safe live checklist.
`target_sha`	string	—	Optional PR or commit SHA for receipt staleness checks.
`target_url`	string	—	Alias for url

Parameters from the server's own tool schema.

RISK

Why geopass_run is rated High

GEOPass performs an active scan/execution against a public URL, making it Execute rather than Read. The tool triggers an external readiness-checking operation with side effects (network requests, analysis execution).

From the tool's definition 'Run GEOPass against a public URL' — the tool executes an external scanning/analysis operation against a specified target URL, triggering analysis and returning structured results.

Risk signalsAccepts URL/endpoint input (url)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs geopass_run 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_run, this is the rule to start with:

geopass_run Rate-limited

geopass_run stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "geopass_run": {
      "limits": [
        {
          "counter": "geopass_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every geopass_run call is checked against it from then on.

FAQ

Questions about geopass_run

What does the geopass_run tool do? +

Run GEOPass against a public URL. Returns a live-readonly AI answer-engine readiness receipt covering answer extractability, entity clarity, citation/sourceability, freshness cues, content structure, llms.txt, and AI bot visibility. GEOPass reports readiness only and does not guarantee rankings or citations. It is categorised as a Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does geopass_run accept? +

geopass_run accepts 4 parameters: url, checks, target_sha, target_url. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on geopass_run? +

Register the UnClick MCP server in PolicyLayer and add a rule for geopass_run: 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.

What risk level is geopass_run? +

geopass_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit geopass_run? +

Yes. Add a rate_limit block to the geopass_run 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.

How do I block geopass_run completely? +

Set action: deny in the PolicyLayer policy for geopass_run. 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.

What MCP server provides geopass_run? +

geopass_run 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.

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 1662 UnClick tools → High-risk tools on this server →

Across the catalogue

run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →