partition_count
Count integer partitions of n with optional max part size and part count constraints.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/partition-count.md
What partition_count does on UnClick
AI agents invoke partition_count 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 |
|---|---|---|---|
n | number | Yes | Non-negative integer to partition (0-10000) |
max_part | number | — | Maximum part size |
num_parts | number | — | Exact number of parts |
Parameters from the server's own tool schema.
Why partition_count is rated High
This tool executes a mathematical algorithm (integer partition counting) rather than simply reading stored data or writing/modifying state. It computes a result based on inputs, making Execute the closest fit. Severity is low as it is a pure computation with no side effects, data access, or destructive capability.
From the tool's definition 'Count integer partitions of n with optional max part size and part count constraints' — performs a mathematical computation
Attacks that exploit this kind of access
The rule that runs partition_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 partition_count, this is the rule to start with:
partition_count 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 partition_count call is checked against it from then on.
Questions about partition_count
Count integer partitions of n with optional max part size and part count constraints. 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.
partition_count accepts 3 parameters: n, max_part, num_parts. Required: n. 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 partition_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.
partition_count 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 partition_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 partition_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.
partition_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.
Across the catalogue