submit_feedback · Clink MCP Server MCP: Risk & Policy

WHAT IT DOES

What submit_feedback does on Clink MCP Server

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

Feedback submission is a write operation that creates new data in the collaboration system. The tool does not delete data (not Destructive), execute arbitrary code (not Execute), or move money (not Financial). Its reversible nature and analogy to other sibling tools indicate Write category.

From the tool's definition Tool name 'submit_feedback' suggests creating or posting feedback data. Description is empty, limiting confidence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit_feedback Rate-limited

submit_feedback 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": {
    "submit_feedback": {
      "limits": [
        {
          "counter": "submit_feedback_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 submit_feedback

What does the submit_feedback tool do? +

submit_feedback. 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 submit_feedback? +

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

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

Can I rate-limit submit_feedback? +

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

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

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