bipartite_check
Check whether an undirected graph is bipartite (2-colorable). Returns the two vertex sets if bipartite, or an odd cycle if not.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/bipartite-check.md
What bipartite_check does on UnClick
AI agents call bipartite_check 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 |
|---|---|---|---|
edges | array | Yes | Undirected edges as [u, v] pairs |
vertices | number | Yes | Number of vertices (0-indexed) |
Parameters from the server's own tool schema.
Why bipartite_check is rated Low
This is a pure computation/analysis tool that reads input (a graph structure) and returns analytical results. It has no side effects, does not execute external code, does not modify data, and does not involve financial transactions. The only risk is if malformed input causes a denial-of-service, but this is a standard read-category limitation.
From the tool's definition Tool performs a graph analysis check ('Check whether an undirected graph is bipartite') and returns results ('Returns the two vertex sets if bipartite, or an odd cycle if not'). No modification, deletion, execution, or financial operations occur.
Attacks that exploit this kind of access
The rule that runs bipartite_check 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 bipartite_check, this is the rule to start with:
bipartite_check 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 bipartite_check call is checked against it from then on.
Questions about bipartite_check
Check whether an undirected graph is bipartite (2-colorable). Returns the two vertex sets if bipartite, or an odd cycle if not. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
bipartite_check accepts 2 parameters: edges, vertices. Required: edges, vertices. 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 bipartite_check: 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.
bipartite_check 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 bipartite_check 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 bipartite_check. 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.
bipartite_check 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