plone_update_content · Plone MCP Server MCP: Risk & Policy

WHAT IT DOES

What plone_update_content does on Plone MCP Server

AI agents use plone_update_content to create or update resources in Plone MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Plone MCP Server environment.

WHY IT NEEDS A POLICY

Why plone_update_content needs a policy

This tool creates or modifies data reversibly by updating existing content items and their metadata/structure. It does not delete data (which would be Destructive), execute arbitrary code (Execute), nor does it handle financial transactions. The 'medium' severity reflects that an AI agent could maliciously alter site content, metadata, or layouts, but changes are reversible via other tools or manual intervention.

From the tool's definition Tool name is 'plone_update_content' and description states it 'Modifies an existing content item in Plone' and can 'update metadata (like title) and/or replace the entire block structure.'

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

plone_update_content Rate-limited

plone_update_content 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": {
    "plone_update_content": {
      "limits": [
        {
          "counter": "plone_update_content_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 Plone MCP Server, so you can run agents against it safely.

FAQ

Questions about plone_update_content

What does the plone_update_content tool do? +

Modifies an existing content item in Plone. Can update metadata (like title) and/or replace the entire block structure. Use. It is categorised as a Write tool in the Plone 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 plone_update_content? +

Register the Plone MCP Server MCP server in PolicyLayer and add a rule for plone_update_content: 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 Plone MCP Server. Nothing to install.

What risk level is plone_update_content? +

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

Can I rate-limit plone_update_content? +

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

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

plone_update_content is provided by the Plone MCP Server MCP server (plone/plone-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.