release_clink · Clink MCP Server MCP: Risk & Policy

WHAT IT DOES

What release_clink does on Clink MCP Server

AI agents use release_clink to create or update resources in Clink MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Clink MCP Server environment.

WHY IT NEEDS A POLICY

Why release_clink needs a policy

This tool updates the status of a clink (task/work item) and returns it to a queue, which is a reversible state modification. It does not execute arbitrary code, delete data permanently, move money, or create new records—it simply transitions an existing claimed clink back to pending status.

From the tool's definition Release a claimed clink without completing it. The clink returns to the pending queue for another worker to process." The tool modifies state by changing the clink's status from claimed to pending, reversibly reassigning work.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

release_clink Rate-limited

release_clink stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "release_clink": {
      "limits": [
        {
          "counter": "release_clink_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Clink MCP Server, so you can run agents against it safely.

FAQ

Questions about release_clink

What does the release_clink tool do? +

Release a claimed clink without completing it. The clink returns to the pending queue for another worker to process. Use this when you cannot complete the task. It is categorised as a Write tool in the Clink MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on release_clink? +

Register the Clink MCP Server MCP server in PolicyLayer and add a rule for release_clink: 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 Clink MCP Server. Nothing to install.

What risk level is release_clink? +

release_clink is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit release_clink? +

Yes. Add a rate_limit block to the release_clink 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.

How do I block release_clink completely? +

Set action: deny in the PolicyLayer policy for release_clink. 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.

What MCP server provides release_clink? +

release_clink is provided by the Clink MCP Server MCP server (voxos-ai-inc/clink-mcp-server-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.