Set tags (labels/statuses) on a Worksection task. Args: - id_task (string, required): Task ID - tags (string, required): Comma-separated tag names or IDs Returns: Confirmation.
AI agents use worksection_set_task_tags 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.
This tool modifies existing task data by adding or updating tags/labels/statuses. This is a reversible operation (tags can be removed or changed later) and does not delete data or execute arbitrary code, making it a Write category. Severity is medium because incorrect tag modifications could affect task organization and workflow visibility, but the impact is limited to metadata and easily reversible.
From the tool's definition Tool sets tags on a task, modifying task metadata. The description states 'Set tags (labels/statuses) on a Worksection task' with required arguments for task ID and tag values, indicating it creates or modifies task properties.
Attacks that exploit this kind of access
Set tags (labels/statuses) on a Worksection task. Args: - id_task (string, required): Task ID - tags (string, required): Comma-separated tag names or IDs 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.
Register the Worksection MCP Server MCP server in PolicyLayer and add a rule for worksection_set_task_tags: 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.
worksection_set_task_tags is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the worksection_set_task_tags 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.
Set action: deny in the PolicyLayer policy for worksection_set_task_tags. 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.
worksection_set_task_tags 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →