Update an existing Confluence page. Requires page ID, new title, and content.
AI agents use confluence_update_page to create or update resources in Atlassian — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Atlassian environment.
This tool creates or modifies data reversibly by updating page content and title in Confluence. It does not delete data (which would be Destructive), execute arbitrary code (Execute), or move money (Financial). The medium severity reflects that misuse could corrupt documentation or spread misinformation across a wiki, but changes are typically recoverable via Confluence's version history.
From the tool's definition Tool name is 'confluence_update_page' and description states 'Update an existing Confluence page.' The word 'update' indicates modification of existing data in a reversible manner.
Documented attack patterns abuse exactly the kind of access confluence_update_page gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Atlassian, and nothing reaches the server without passing your rules. This is the rule we recommend for confluence_update_page:
{
"version": "1",
"default": "deny",
"tools": {
"confluence_update_page": {
"limits": [
{
"counter": "confluence_update_page_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}confluence_update_page 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 an existing Confluence page. Requires page ID, new title, and content. It is categorised as a Write tool in the Atlassian MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Atlassian MCP server in PolicyLayer and add a rule for confluence_update_page: 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 Atlassian. Nothing to install.
confluence_update_page 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 confluence_update_page 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 confluence_update_page. 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.
confluence_update_page is provided by the Atlassian MCP server (xuanxt/atlassian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Atlassian, 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.
51 Atlassian tools catalogued and risk-classified — across an index of 43,000+ MCP servers.