chromatic_number
Compute the exact chromatic number of a graph using inclusion-exclusion (up to 20 vertices).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/chromatic-number.md
What chromatic_number does on UnClick
AI agents invoke chromatic_number 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 |
|---|---|---|---|
edges | array | Yes | Edges as [u, v] pairs (0-indexed) |
vertex_count | number | Yes | Number of vertices (max 20) |
Parameters from the server's own tool schema.
Why chromatic_number is rated High
This tool executes a non-trivial graph-theoretic computation (inclusion-exclusion algorithm) on provided input. It has no data read/write/destructive side effects, but it does perform active computation/execution rather than merely retrieving stored data. Severity is low as the blast radius of misuse is minimal — it only computes a mathematical result.
From the tool's definition 'Compute the exact chromatic number of a graph using inclusion-exclusion (up to 20 vertices)' — runs a computational algorithm
Attacks that exploit this kind of access
The rule that runs chromatic_number 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 chromatic_number, this is the rule to start with:
chromatic_number 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 chromatic_number call is checked against it from then on.
Questions about chromatic_number
Compute the exact chromatic number of a graph using inclusion-exclusion (up to 20 vertices). 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.
chromatic_number accepts 2 parameters: edges, vertex_count. Required: edges, vertex_count. 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 chromatic_number: 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.
chromatic_number 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 chromatic_number 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 chromatic_number. 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.
chromatic_number 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