copypass_status
Fetch the current status, notes, deterministic findings, disclaimer, copypass_receipt_v1 proof envelope, and CopyRoom receipt for a CopyPass run started in this MCP session.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/copypass-status.md
What copypass_status does on UnClick
AI agents call copypass_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 run id returned by copypass_run |
Parameters from the server's own tool schema.
Why copypass_status is rated Low
This tool performs read-only queries of status and receipt information for a CopyPass run. It retrieves existing data without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an agent could only view information it should not access, not alter systems or trigger external actions. This fits the Read category.
From the tool's definition Tool description uses 'Fetch the current status' and retrieves 'status, notes, findings, disclaimer, proof envelope, and receipt' — all data retrieval operations with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
The rule that runs copypass_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 copypass_status, this is the rule to start with:
copypass_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 copypass_status call is checked against it from then on.
Questions about copypass_status
Fetch the current status, notes, deterministic findings, disclaimer, copypass_receipt_v1 proof envelope, and CopyRoom receipt for a CopyPass run started in this MCP session. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
copypass_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 copypass_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.
copypass_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 copypass_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 copypass_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.
copypass_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