worksection_reopen_task · Worksection MCP Server MCP

WHAT IT DOES

What worksection_reopen_task does on Worksection MCP Server

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

WHY IT NEEDS A POLICY

Why worksection_reopen_task needs a policy

Reopening a completed task modifies the task's state from completed back to open. This is a reversible write operation — it changes task status but does not delete or destroy any data, and the action itself can be undone by completing the task again. Severity is medium as an AI agent could incorrectly reopen tasks en masse, disrupting project workflows.

From the tool's definition Reopen a previously completed task

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

worksection_reopen_task Rate-limited

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

FAQ

Questions about worksection_reopen_task

What does the worksection_reopen_task tool do? +

Reopen a previously completed task. Args: - id_task (string, required): Task ID to reopen Returns: Confirmation. It is categorised as a Write tool in the Worksection MCP 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 worksection_reopen_task? +

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

What risk level is worksection_reopen_task? +

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

Can I rate-limit worksection_reopen_task? +

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

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

worksection_reopen_task is provided by the Worksection MCP Server MCP server (novgorodskii/worksection-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.