mark_tasks_done · Subconductor MCP: Risk & Policy

WHAT IT DOES

What mark_tasks_done does on Subconductor

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

WHY IT NEEDS A POLICY

Why mark_tasks_done needs a policy

The tool modifies existing data (task completion status) in a checklist/workflow system, which is a Write operation. It is not Destructive because marking tasks done does not irreversibly delete data and can be reversed.

From the tool's definition Tool name 'mark_tasks_done' and description indicate batch modification of task state to 'completed'. This is a write operation that updates task records reversibly (tasks can be marked undone or reset).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mark_tasks_done Rate-limited

mark_tasks_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": {
    "mark_tasks_done": {
      "limits": [
        {
          "counter": "mark_tasks_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 Subconductor, so you can run agents against it safely.

FAQ

Questions about mark_tasks_done

What does the mark_tasks_done tool do? +

Mark multiple tasks as completed in a single batch operation. You can reference tasks by their ID (e.g.,. It is categorised as a Write tool in the Subconductor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on mark_tasks_done? +

Register the Subconductor MCP server in PolicyLayer and add a rule for mark_tasks_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 Subconductor. Nothing to install.

What risk level is mark_tasks_done? +

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

Can I rate-limit mark_tasks_done? +

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

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

mark_tasks_done is provided by the Subconductor MCP server (paulbenchea/mcp-subconductor). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.