bit_count
Count set bits (popcount), total bits, and convert between decimal, binary, hex, and octal. Detects powers of two.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/bit-count.md
What bit_count does on UnClick
AI agents call bit_count 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 |
|---|---|---|---|
value | string | Yes | Integer or binary/hex string (e.g. 42, 0xFF, 0b1010) |
Parameters from the server's own tool schema.
Why bit_count is rated Low
This is a mathematical utility function that reads numeric input and returns computed results. It has no ability to modify state, execute arbitrary code, access external systems, or cause any side effects. The operations are idempotent and informational only, placing it clearly in the Read category with low severity.
From the tool's definition Tool performs bit counting (popcount), total bit counting, and number format conversion (decimal, binary, hex, octal) with power-of-two detection.
Attacks that exploit this kind of access
The rule that runs bit_count 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 bit_count, this is the rule to start with:
bit_count 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 bit_count call is checked against it from then on.
Questions about bit_count
Count set bits (popcount), total bits, and convert between decimal, binary, hex, and octal. Detects powers of two. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
bit_count accepts 1 parameter: value. Required: value. 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 bit_count: 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.
bit_count 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 bit_count 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 bit_count. 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.
bit_count 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