worksection_post_comment · Worksection MCP Server MCP

WHAT IT DOES

What worksection_post_comment does on Worksection MCP Server

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

This tool creates new comment records, which is a reversible write operation. It does not delete, overwrite irreversibly, execute arbitrary code, move money, or trigger external side effects beyond creating a comment artifact. The impact is limited to adding discussion/documentation to a task, with low blast radius if misused (e.g., spam comments).

From the tool's definition Tool creates/adds a comment to a task ('Add a comment to a Worksection task'). The args show it writes new data (text, optional todo items) to an existing task. The return value is 'Created comment data', confirming data creation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

worksection_post_comment Rate-limited

worksection_post_comment 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_post_comment": {
      "limits": [
        {
          "counter": "worksection_post_comment_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_post_comment

What does the worksection_post_comment tool do? +

Add a comment to a Worksection task. Args: - id_task (string, required): Task ID to comment on - text (string, required): Comment text content - todo (string, optional): Checklist items, one per line (creates checkboxes in the comment) - email_user_from (string, optional): Email of the comment author (defaults to API key owner) Returns: Created comment data. 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_post_comment? +

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

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

Can I rate-limit worksection_post_comment? +

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

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

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