securitypass_verify_scope
Verify scope authorisation for a target via DNS TXT or /.well-known proof. Required before any active probe runs.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/securitypass-verify-scope.md
What securitypass_verify_scope does on UnClick
AI agents call securitypass_verify_scope 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 |
|---|---|---|---|
target_url | string | — | |
contract_id | string | — | Signed scope contract id |
target_repo | string | — | |
target_type | string | — | |
proof_method | string | Yes | |
expected_token | string | — | Token to look for in DNS TXT or /.well-known |
proof_timeout_ms | number | — | Optional timeout for well-known proof fetches |
Parameters from the server's own tool schema.
Why securitypass_verify_scope is rated Low
The tool performs verification by reading DNS TXT records and checking well-known configuration files. This is a read operation with no data modification, deletion, or execution of arbitrary code. It is a security check mechanism, not a capability to perform actions. Even though it precedes active probes, this particular tool itself only reads existing data to determine authorization eligibility.
From the tool's definition Tool description states it 'verifies scope authorisation...via DNS TXT or /.well-known proof' and is 'required before any active probe runs.' This is a pre-flight check that queries DNS records and well-known files to validate authorization—read-only…
Attacks that exploit this kind of access
The rule that runs securitypass_verify_scope 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 securitypass_verify_scope, this is the rule to start with:
securitypass_verify_scope 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 securitypass_verify_scope call is checked against it from then on.
Questions about securitypass_verify_scope
Verify scope authorisation for a target via DNS TXT or /.well-known proof. Required before any active probe runs. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
securitypass_verify_scope accepts 7 parameters: target_url, contract_id, target_repo, target_type, proof_method, expected_token, proof_timeout_ms. Required: proof_method. 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 securitypass_verify_scope: 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.
securitypass_verify_scope 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 securitypass_verify_scope 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 securitypass_verify_scope. 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.
securitypass_verify_scope 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