done · MCP Backlog Server MCP: Risk & Policy

WHAT IT DOES

What done does on MCP Backlog Server

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

WHY IT NEEDS A POLICY

Why done needs a policy

This tool updates the status of backlog items to 'complete', which is a reversible data modification (status can be changed back). It does not delete or destroy data, execute code, or involve financial transactions. The severity is medium because marking items done affects workflow state and could mislead project tracking if misused.

From the tool's definition Mark backlog items as complete with optional summary - done operation and list

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

done Rate-limited

done 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": {
    "done": {
      "limits": [
        {
          "counter": "done_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 MCP Backlog Server, so you can run agents against it safely.

FAQ

Questions about done

What does the done tool do? +

Mark backlog items as complete with optional summary - done operation and list. It is categorised as a Write tool in the MCP Backlog 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 done? +

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

What risk level is done? +

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

Can I rate-limit done? +

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

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

done is provided by the MCP Backlog Server MCP server (rwese/mcp-backlog). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.