worksection_complete_task · Worksection MCP Server MCP

WHAT IT DOES

What worksection_complete_task does on Worksection MCP Server

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

The tool modifies task metadata (status field) rather than creating new data (Write not Execute). It's reversible (a completed task can be reopened), so it's not Destructive. No code execution, financial transactions, or irreversible deletions are involved.

From the tool's definition Tool name 'worksection_complete_task' and description 'Mark a task as completed (done)' indicates modifying task status. This is a state change operation that updates data reversibly — tasks can be marked incomplete or reopened if needed.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

worksection_complete_task Rate-limited

worksection_complete_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_complete_task": {
      "limits": [
        {
          "counter": "worksection_complete_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_complete_task

What does the worksection_complete_task tool do? +

Mark a task as completed (done). Args: - id_task (string, required): Task ID to complete 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_complete_task? +

Register the Worksection MCP Server MCP server in PolicyLayer and add a rule for worksection_complete_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_complete_task? +

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

Can I rate-limit worksection_complete_task? +

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

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

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