Update an existing version
AI agents use update_version to create or update resources in Tonle OpenProject MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tonle OpenProject MCP Server environment.
This tool modifies existing version records (e.g., version metadata, status, dates) in OpenProject. Updates are reversible—data can be changed again or reverted. It does not delete data (which would be Destructive), execute arbitrary code (Execute), move money (Financial), or trigger uncontrollable side effects.
From the tool's definition Tool description: 'Update an existing version'. The verb 'update' indicates modification of existing data in a reversible manner, consistent with the Write category.
Attacks that exploit this kind of access
Update an existing version. It is categorised as a Write tool in the Tonle OpenProject MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tonle OpenProject MCP Server MCP server in PolicyLayer and add a rule for update_version: 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 Tonle OpenProject MCP Server. Nothing to install.
update_version 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 update_version 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 update_version. 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.
update_version is provided by the Tonle OpenProject MCP Server MCP server (liratanak/openproject-mcp). 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 →