commonsensepass_rules
Return the worker-readable CommonSensePass rules, verdict vocabulary, and fixture ids. Set include_fixtures=true for full example packets.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/commonsensepass-rules.md
What commonsensepass_rules does on UnClick
AI agents call commonsensepass_rules 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 |
|---|---|---|---|
include_fixtures | boolean | — | Include full deterministic worker fixture packets. |
Parameters from the server's own tool schema.
Why commonsensepass_rules is rated Low
This tool only reads and returns static reference data (rules, vocabulary, fixture IDs). There are no write, execute, or destructive operations indicated. The optional parameter 'include_fixtures=true' only adds example packets to the response, still a read operation.
From the tool's definition 'Return the worker-readable CommonSensePass rules, verdict vocabulary, and fixture ids' — purely retrieves configuration/reference data with no side effects
Attacks that exploit this kind of access
The rule that runs commonsensepass_rules 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_rules, this is the rule to start with:
commonsensepass_rules 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_rules call is checked against it from then on.
Questions about commonsensepass_rules
Return the worker-readable CommonSensePass rules, verdict vocabulary, and fixture ids. Set include_fixtures=true for full example packets. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
commonsensepass_rules accepts 1 parameter: include_fixtures. 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 commonsensepass_rules: 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_rules 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_rules 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_rules. 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_rules 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