bitwise_calc
Perform bitwise operations (AND, OR, XOR, NOT, NAND, NOR, shifts) on integers.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/bitwise-calc.md
What bitwise_calc does on UnClick
AI agents invoke bitwise_calc 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 |
|---|---|---|---|
a | number | Yes | First integer. |
b | number | — | Second integer (not needed for NOT). |
operation | string | — | Operation: and, or, xor, not, nand, nor, shift_left, shift_right (default and). |
Parameters from the server's own tool schema.
Why bitwise_calc is rated High
This tool executes mathematical/logical computations on input integers. It doesn't read from a data store, write persistent data, or cause destructive/financial side effects. It runs a computation and returns a result, placing it in the Execute category. Blast radius is low since it only performs in-memory arithmetic with no external side effects.
From the tool's definition Perform bitwise operations (AND, OR, XOR, NOT, NAND, NOR, shifts) on integers
Attacks that exploit this kind of access
The rule that runs bitwise_calc 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 bitwise_calc, this is the rule to start with:
bitwise_calc 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 bitwise_calc call is checked against it from then on.
Questions about bitwise_calc
Perform bitwise operations (AND, OR, XOR, NOT, NAND, NOR, shifts) on integers. 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.
bitwise_calc accepts 3 parameters: a, b, operation. Required: a. 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 bitwise_calc: 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.
bitwise_calc 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 bitwise_calc 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 bitwise_calc. 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.
bitwise_calc 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