compliancepass_run
Run CompliancePass against a local repo path. Returns evidence-backed readiness guidance, gaps, next actions, and an in-session run id. Historical EnterprisePass references are treated as this same product.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/compliancepass-run.md
What compliancepass_run does on UnClick
AI agents invoke compliancepass_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 |
|---|---|---|---|
repo_path | string | — | Local repository path to scan. Defaults to the MCP server working directory. |
target_sha | string | — | Optional PR or commit SHA for receipt staleness checks |
target_name | string | — | Human-readable target name for the report. Defaults to UnClick. |
Parameters from the server's own tool schema.
Why compliancepass_run is rated High
This tool executes a compliance scanning operation on local repositories. While it does not directly delete, modify, or move money, it runs an external process/analysis whose behavior depends on arguments supplied by the agent. This fits the Execute category (runs code or triggers external operations).
From the tool's definition Tool name includes 'run' and description states 'Run CompliancePass against a local repo path'. The tool executes an external compliance analysis operation on a specified repository, which is a triggered operation whose effects depend on the target path…
Attacks that exploit this kind of access
The rule that runs compliancepass_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 compliancepass_run, this is the rule to start with:
compliancepass_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 compliancepass_run call is checked against it from then on.
Questions about compliancepass_run
Run CompliancePass against a local repo path. Returns evidence-backed readiness guidance, gaps, next actions, and an in-session run id. Historical EnterprisePass references are treated as this same product. 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.
compliancepass_run accepts 3 parameters: repo_path, target_sha, target_name. 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 compliancepass_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.
compliancepass_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 compliancepass_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 compliancepass_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.
compliancepass_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