compliancepass_status
Fetch the stored in-session status and summary for a CompliancePass run.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/compliancepass-status.md
What compliancepass_status does on UnClick
AI agents call compliancepass_status 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 |
|---|---|---|---|
run_id | string | Yes | The CompliancePass run id returned by compliancepass_run |
Parameters from the server's own tool schema.
Why compliancepass_status is rated Low
This tool retrieves compliance status information from a CompliancePass session. The verb "Fetch" combined with "stored...status and summary" indicates a read-only query operation that returns data without modifying, creating, deleting, or executing anything. No side effects or state changes are implied. Low severity because reading status data presents minimal risk even if misused by an agent.
From the tool's definition Tool name and description both indicate a retrieval operation: "Fetch the stored in-session status and summary" explicitly describes querying/retrieving data with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs compliancepass_status 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_status, this is the rule to start with:
compliancepass_status 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 compliancepass_status call is checked against it from then on.
Questions about compliancepass_status
Fetch the stored in-session status and summary for a CompliancePass run. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
compliancepass_status accepts 1 parameter: run_id. Required: run_id. 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_status: 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_status 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 compliancepass_status 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_status. 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_status 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