Update an existing document by its documentId. This is a write operation.
AI agents use update to create or update resources in Strapi Content MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Strapi Content MCP environment.
The tool creates or modifies data reversibly through the update operation on CMS documents. While it can change content, the changes are not irreversible (can be updated again or reverted), making it Write rather than Destructive. Severity is medium because unintended updates could alter live content, but the impact is limited to individual documents and reversible with proper access controls.
From the tool's definition Tool description explicitly states 'This is a write operation' and function name 'update' modifies existing documents by documentId in a Strapi CMS.
Attacks that exploit this kind of access
Update an existing document by its documentId. This is a write operation. It is categorised as a Write tool in the Strapi Content MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Strapi Content MCP server in PolicyLayer and add a rule for update: 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 Strapi Content MCP. Nothing to install.
update 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 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. 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 is provided by the Strapi Content MCP server (paulbratslavsky/strapi-content-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 →