securitypass_run
Start a scope-gated SecurityPass scan against a registered pack or target URL. Returns a safe securitypass_receipt_v1 proof envelope without raw secrets or PoC payloads.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/securitypass-run.md
What securitypass_run does on UnClick
AI agents invoke securitypass_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 |
|---|---|---|---|
pack_id | string | — | Pack id, e.g. 'securitypass-web-baseline' |
profile | string | — | |
pack_yaml | string | — | Optional pack YAML to validate and run without prior registration |
target_id | string | — | Target id inside the SecurityPass pack |
target_url | string | — | Target URL (must be in pack scope) |
contract_id | string | — | Scope contract id for skeleton URL scans |
proof_method | string | — | |
expected_token | string | — | Expected scope proof token |
proof_timeout_ms | number | — | Optional timeout for well-known proof fetches |
Parameters from the server's own tool schema.
Why securitypass_run is rated High
This tool executes a security scanning operation against user-specified targets. While the scan itself is gated and returns a safe proof envelope (mitigating information disclosure risk), it initiates external automated testing that could impact target systems or services.
From the tool's definition Tool description states 'Start a scope-gated SecurityPass scan' — the verb 'Start' combined with 'scan' indicates execution of an external security scanning operation.
Attacks that exploit this kind of access
The rule that runs securitypass_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 securitypass_run, this is the rule to start with:
securitypass_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.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every securitypass_run call is checked against it from then on.
Questions about securitypass_run
Start a scope-gated SecurityPass scan against a registered pack or target URL. Returns a safe securitypass_receipt_v1 proof envelope without raw secrets or PoC payloads. 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.
securitypass_run accepts 9 parameters: pack_id, profile, pack_yaml, target_id, target_url, contract_id, proof_method, expected_token, proof_timeout_ms. 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_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.
securitypass_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the securitypass_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.
Set action: deny in the PolicyLayer policy for securitypass_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.
securitypass_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.
More on UnClick, and thousands of servers like it.
Across the catalogue