Mark a specific task as completed in the active checklist. You can reference the task by its ID (e.g.,
AI agents use mark_task_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.
This tool creates a reversible state change in a checklist—marking a task as done can be undone by unmarking or resetting it. It does not delete data, execute arbitrary code, transfer funds, or perform irreversible operations. This is a straightforward data modification action, placing it in the Write category with low severity due to limited blast radius (affects only task state within a single checklist).
From the tool's definition Tool description states 'Mark a specific task as completed in the active checklist', which modifies task state by updating a task record from incomplete to completed status.
Attacks that exploit this kind of access
Mark a specific task as completed in the active checklist. You can reference the task by its 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.
Register the Subconductor MCP server in PolicyLayer and add a rule for mark_task_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.
mark_task_done is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the mark_task_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.
Set action: deny in the PolicyLayer policy for mark_task_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.
mark_task_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.
mark_task_done is one line of Subconductor's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →