complete_clink · Clink MCP Server MCP: Risk & Policy

WHAT IT DOES

What complete_clink does on Clink MCP Server

AI agents use complete_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 complete_clink needs a policy

This tool creates or modifies data (marks completion status, optionally adds a reply message) without permanently destroying data or executing arbitrary code. The operations are reversible state changes within a collaboration/messaging system. While it updates records, the impact is limited to the user's own clink and optional replies within an established group messaging context.

From the tool's definition Tool description states 'Mark a claimed clink as completed' and 'send a reply' — operations that modify state (completing a task, posting a message) but are reversible.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

complete_clink Rate-limited

complete_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": {
    "complete_clink": {
      "limits": [
        {
          "counter": "complete_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 complete_clink

What does the complete_clink tool do? +

Mark a claimed clink as completed. You must have claimed the clink first. Optionally send a reply to the original sender. 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 complete_clink? +

Register the Clink MCP Server MCP server in PolicyLayer and add a rule for complete_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 complete_clink? +

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

Can I rate-limit complete_clink? +

Yes. Add a rate_limit block to the complete_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 complete_clink completely? +

Set action: deny in the PolicyLayer policy for complete_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 complete_clink? +

complete_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.