Update the content of a Confluence page
AI agents use update_page_content to create or update resources in Confluence Communication Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Confluence Communication Server environment.
This tool creates or modifies data reversibly by updating page content in Confluence. It does not delete data (would be Destructive) nor does it execute arbitrary code (would be Execute). The modification is reversible through Confluence's version history.
From the tool's definition Tool name explicitly states 'update' and description states 'Update the content of a Confluence page' — direct modification of existing data.
Documented attack patterns abuse exactly the kind of access update_page_content gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Confluence Communication Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_page_content:
{
"version": "1",
"default": "deny",
"tools": {
"update_page_content": {
"limits": [
{
"counter": "update_page_content_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_page_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.
Free to start. No card required.
Update the content of a Confluence page. It is categorised as a Write tool in the Confluence Communication Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Confluence Communication Server MCP server in PolicyLayer and add a rule for update_page_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 Confluence Communication Server. Nothing to install.
update_page_content 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_page_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.
Set action: deny in the PolicyLayer policy for update_page_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.
update_page_content is provided by the Confluence Communication Server MCP server (ks-gen-ai/confluence-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Confluence Communication Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 Confluence Communication Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.