Update an existing Worksection project. Only provided fields will be updated. Args: - id_project (string, required): Project ID - title (string, optional): New project name - email_manager (string, optional): New project manager email - text (string, optional): New description - date_start (strin...
AI agents use worksection_update_project 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 project data (name, manager, description, dates) but does not delete data or trigger financial transactions. Updates are reversible—previous values can be restored by calling the tool again. This qualifies as Write rather than Execute (no code/command execution) or Destructive (data remains intact).
From the tool's definition Tool description explicitly states 'Update an existing Worksection project' with optional fields for title, email_manager, text, date_start, and date_end. These are reversible modifications to project metadata.
Attacks that exploit this kind of access
Update an existing Worksection project. Only provided fields will be updated. Args: - id_project (string, required): Project ID - title (string, optional): New project name - email_manager (string, optional): New project manager email - text (string, optional): New description - date_start (string, optional): New start date YYYY-MM-DD - date_end (string, optional): New due date YYYY-MM-DD Returns: Updated project 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.
Register the Worksection MCP Server MCP server in PolicyLayer and add a rule for worksection_update_project: 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_update_project 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_update_project 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_update_project. 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_update_project 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 →