unmark_tasks · Subconductor MCP: Risk & Policy

WHAT IT DOES

What unmark_tasks does on Subconductor

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

This tool modifies state in the checklist/task management system by changing task status from completed back to pending. While reversible (tasks can be marked done again), it alters persistent workflow state and could disrupt task tracking if misused by an agent. It does not permanently delete data (would be Destructive) nor execute arbitrary code (would be Execute).

From the tool's definition Tool 'unmark_tasks' performs a batch operation that reverts completed tasks back to pending status. The description states it modifies task state (reverting from 'completed' to 'pending'), which constitutes data modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

unmark_tasks Rate-limited

unmark_tasks 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_tasks": {
      "limits": [
        {
          "counter": "unmark_tasks_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_tasks

What does the unmark_tasks tool do? +

Revert multiple completed tasks back to pending status 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 unmark_tasks? +

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

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

Can I rate-limit unmark_tasks? +

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

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

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