min_vertex_cover
Find the minimum vertex cover of a graph using exact bitmask enumeration (up to 20 vertices).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/min-vertex-cover.md
What min_vertex_cover does on UnClick
AI agents invoke min_vertex_cover 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 |
vertex_count | number | Yes | Number of vertices (max 20) |
Parameters from the server's own tool schema.
Why min_vertex_cover is rated High
This tool performs a computation (bitmask enumeration algorithm) on input data to find a minimum vertex cover. It executes a potentially expensive algorithm but has no side effects on external systems, data stores, or finances. It is more than a simple read/query of stored data — it runs an algorithm — so Execute is most appropriate.
From the tool's definition 'Find the minimum vertex cover of a graph using exact bitmask enumeration' — runs a computational algorithm on provided graph input
Attacks that exploit this kind of access
The rule that runs min_vertex_cover 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 min_vertex_cover, this is the rule to start with:
min_vertex_cover 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 min_vertex_cover call is checked against it from then on.
Questions about min_vertex_cover
Find the minimum vertex cover of a graph using exact bitmask enumeration (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.
min_vertex_cover 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 min_vertex_cover: 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.
min_vertex_cover 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 min_vertex_cover 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 min_vertex_cover. 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.
min_vertex_cover 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