Plan a LegalPass issue-spotting run against a URL, contract upload, or repo. Scaffold-only: exposes LegalPass guardrails and the safe run envelope while full 12-hat execution lands in a later engine chip.
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 | Yes | |
pack_id | string | — | LegalPass pack slug (default: legalpass-mvp-v0) |
profile | string | — | Run profile (default: smoke) |
jurisdictions | array | — | Optional jurisdiction routing hints |
Parameters from the server's own tool schema.
This tool executes an external analysis service (LegalPass issue-spotting) on user-specified targets. While currently described as 'scaffold-only' with guardrails in place, it still triggers code execution.
From the tool's definition Tool description states 'Plan a LegalPass issue-spotting run' which involves triggering analysis against user-supplied inputs (URL, contract upload, or repo).
Risk signalsAccepts URL/endpoint input (target.url) · High parameter count (10 properties)
Attacks that exploit this kind of access
Plan a LegalPass issue-spotting run against a URL, contract upload, or repo. Scaffold-only: exposes LegalPass guardrails and the safe run envelope while full 12-hat execution lands in a later engine chip. 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 4 parameters: target, pack_id, profile, jurisdictions. Required: target. 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →