Update an existing Confluence page. Requires current version number (will be auto-incremented).
AI agents use confluence_update_page to create or update resources in Sage MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sage MCP environment.
This tool modifies existing data (a Confluence page) in a reversible manner. It is a Write operation because updates can typically be undone by reverting to previous versions.
From the tool's definition Tool name 'confluence_update_page' and description 'Update an existing Confluence page' indicate modification of existing content. The mention of 'current version number (will be auto-incremented)' confirms this is a reversible update operation, not deletion.
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 Sage MCP, 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 current version number (will be auto-incremented). It is categorised as a Write tool in the Sage MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sage 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 Sage MCP. 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 Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.