unmark_task · Subconductor MCP: Risk & Policy

WHAT IT DOES

What unmark_task does on Subconductor

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

This tool modifies data (task status) in a reversible manner without deleting or destroying information, placing it in the Write category. Severity is low because the blast radius of misuse is confined to workflow state management with no external side effects, financial impact, or irreversible consequences. The modification can be easily undone by re-marking the task as done.

From the tool's definition Tool 'unmark_task' reverts a completed task back to pending status. The description indicates it modifies task state from completed to pending, a reversible state change within the checklist system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

unmark_task Rate-limited

unmark_task 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": {
    "unmark_task": {
      "limits": [
        {
          "counter": "unmark_task_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 unmark_task

What does the unmark_task tool do? +

Revert a completed task back to pending status 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.

How do I enforce a policy on unmark_task? +

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

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

Can I rate-limit unmark_task? +

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

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

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