legalpass_run
Run a LegalPass issue-spotting pass against a URL, contract upload, or repo. With fixture_text, returns deterministic public evidence; without it, returns the guarded run plan.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/legalpass-run.md
What legalpass_run does on UnClick
AI agents invoke legalpass_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 |
|---|---|---|---|
target | object | — | |
pack_id | string | — | LegalPass pack slug (default: legalpass-mvp-v0) |
profile | string | — | Run profile (default: smoke) |
target_sha | string | — | Optional commit or target evidence SHA to bind the LegalPass receipt to a specific target version |
target_url | string | — | URL target shortcut for TestPass-style callers |
fixture_text | string | — | Public text to check deterministically for dogfood or local proof |
jurisdictions | array | — | Optional jurisdiction routing hints |
Parameters from the server's own tool schema.
Why legalpass_run is rated High
This tool executes a legal analysis/scanning operation against user-supplied inputs (URLs, contracts, repositories). While the analysis itself is not destructive or financial, it performs a computation/scan operation triggered by the tool invocation, making it Execute rather than Read.
From the tool's definition Tool description explicitly states 'Run a LegalPass issue-spotting pass' against URLs, contract uploads, or repositories.
Risk signalsAccepts URL/endpoint input (target.url) · High parameter count (13 properties)
Attacks that exploit this kind of access
The rule that runs legalpass_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 legalpass_run, this is the rule to start with:
legalpass_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 legalpass_run call is checked against it from then on.
Questions about legalpass_run
Run a LegalPass issue-spotting pass against a URL, contract upload, or repo. With fixture_text, returns deterministic public evidence; without it, returns the guarded run plan. 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.
legalpass_run accepts 7 parameters: target, pack_id, profile, target_sha, target_url, fixture_text, jurisdictions. 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 legalpass_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.
legalpass_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 legalpass_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 legalpass_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.
legalpass_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