commonsensepass_protocol
Returns the canonical CommonSensePass worker sanity-gate playbook. Call this when a worker needs to decide if a healthy, no_work, done, merge_ready, pass, quiet, or duplicate_wake claim makes sense.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/commonsensepass-protocol.md
What commonsensepass_protocol does on UnClick
AI agents call commonsensepass_protocol 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.
Why commonsensepass_protocol is rated Low
This tool retrieves or queries an internal decision framework (a playbook) to help workers evaluate claim statuses. It has no ability to modify data, execute external operations, delete records, or move money. The function is purely informational—returning canonical guidance for decision-making logic. This is a straightforward Read operation with minimal blast radius.
From the tool's definition Tool name and description indicate it 'Returns' a playbook/decision framework. Keywords: 'Returns the canonical...playbook' and 'decide if...makes sense' suggest data retrieval and logic query with no side effects.
Attacks that exploit this kind of access
The rule that runs commonsensepass_protocol 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 commonsensepass_protocol, this is the rule to start with:
commonsensepass_protocol 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 commonsensepass_protocol call is checked against it from then on.
Questions about commonsensepass_protocol
Returns the canonical CommonSensePass worker sanity-gate playbook. Call this when a worker needs to decide if a healthy, no_work, done, merge_ready, pass, quiet, or duplicate_wake claim makes sense. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
Register the UnClick MCP server in PolicyLayer and add a rule for commonsensepass_protocol: 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.
commonsensepass_protocol 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 commonsensepass_protocol 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 commonsensepass_protocol. 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.
commonsensepass_protocol 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