bitwise
Bitwise Operations — AND, OR, XOR, NOT, shift, and popcount on integers with configurable bit width.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/bitwise.md
What bitwise does on Gateway
AI agents invoke bitwise to trigger actions in Gateway. 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 | integer | Yes | First integer |
b | integer | — | Second integer / shift amount |
op | string | — | Bitwise op |
bits | integer | — | Bit width for not/popcount (default 8) |
Parameters from the server's own tool schema.
Why bitwise is rated High
This tool performs computational operations (bitwise logic and arithmetic) on integer inputs. It executes calculations rather than merely reading stored data or writing/modifying persistent state. The blast radius is low since it only processes numeric inputs and returns results with no side effects on external systems.
From the tool's definition Bitwise Operations — AND, OR, XOR, NOT, shift, and popcount on integers with configurable bit width.
Attacks that exploit this kind of access
The rule that runs bitwise safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bitwise, this is the rule to start with:
bitwise 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 Gateway, apply this rule, and every bitwise call is checked against it from then on.
Questions about bitwise
Bitwise Operations — AND, OR, XOR, NOT, shift, and popcount on integers with configurable bit width. It is categorised as a Execute tool in the Gateway MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
bitwise accepts 4 parameters: a, b, op, bits. Required: a. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for bitwise: 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 Gateway. Nothing to install.
bitwise 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 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. 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 is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
Across the catalogue