bitmask_ops
Bitmask operations: info, submasks, supersets, next permutation, enumerate set bits.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/bitmask-ops.md
What bitmask_ops does on UnClick
AI agents invoke bitmask_ops 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 |
|---|---|---|---|
mask | number | Yes | Non-negative integer bitmask |
universe | number | — | Universe mask for supersets operation |
operation | string | Yes | Operation: info, submasks, supersets, next_permutation, or enumerate |
Parameters from the server's own tool schema.
Why bitmask_ops is rated High
This tool performs computational operations (bit manipulation, enumeration, permutation) on provided data. It doesn't read from or write to external storage, but it executes logic/calculations. The blast radius is low since it's pure computation with no side effects on external systems.
From the tool's definition Bitmask operations: info, submasks, supersets, next permutation, enumerate set bits.
Attacks that exploit this kind of access
The rule that runs bitmask_ops 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 bitmask_ops, this is the rule to start with:
bitmask_ops 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 bitmask_ops call is checked against it from then on.
Questions about bitmask_ops
Bitmask operations: info, submasks, supersets, next permutation, enumerate set bits. 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.
bitmask_ops accepts 3 parameters: mask, universe, operation. Required: mask, operation. 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 bitmask_ops: 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.
bitmask_ops 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 bitmask_ops 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 bitmask_ops. 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.
bitmask_ops 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