necklace_count
Count distinct necklaces and bracelets using Burnside's lemma.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/necklace-count.md
What necklace_count does on UnClick
AI agents call necklace_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 |
|---|---|---|---|
k | number | Yes | Number of colors (1-1000) |
n | number | Yes | Length (1-1000) |
Parameters from the server's own tool schema.
Why necklace_count is rated Low
This tool performs a pure computational task (combinatorial counting using Burnside's lemma, a mathematical theorem). It takes input parameters and returns a computed result. There are no side effects—no data is created, modified, deleted, or persisted. No external systems are invoked. This is a classic Read operation: retrieving a computed answer.
From the tool's definition Tool name 'necklace_count' and description 'Count distinct necklaces and bracelets using Burnside's lemma' indicate a mathematical computation that retrieves or calculates a result without modifying any data or triggering external operations.
Attacks that exploit this kind of access
The rule that runs necklace_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 necklace_count, this is the rule to start with:
necklace_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 necklace_count call is checked against it from then on.
Questions about necklace_count
Count distinct necklaces and bracelets using Burnside's lemma. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
necklace_count accepts 2 parameters: k, n. Required: k, 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 necklace_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.
necklace_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 necklace_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 necklace_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.
necklace_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