confluence_update_page · Jira & Confluence MCP Server MCP

WHAT IT DOES

What confluence_update_page does on Jira & Confluence MCP Server

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

WHY IT NEEDS A POLICY

Why confluence_update_page needs a policy

Updating a page is a Write operation: it creates or modifies data in a reversible manner. The change can be undone (reverted to previous versions in Confluence). Severity is medium because uncontrolled updates could corrupt documentation or overwrite important content, but the effect is not irreversible like deletion and does not involve financial transactions or code execution with unpredictable side effects.

From the tool's definition Tool name is 'confluence_update_page' and description states 'Update an existing Confluence page' — this modifies existing data reversibly without deleting it.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

confluence_update_page Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "confluence_update_page": {
      "limits": [
        {
          "counter": "confluence_update_page_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 Jira & Confluence MCP Server, so you can run agents against it safely.

FAQ

Questions about confluence_update_page

What does the confluence_update_page tool do? +

Update an existing Confluence page. It is categorised as a Write tool in the Jira & Confluence 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 confluence_update_page? +

Register the Jira & Confluence MCP Server 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 Jira & Confluence MCP Server. Nothing to install.

What risk level is confluence_update_page? +

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

Can I rate-limit confluence_update_page? +

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.

How do I block confluence_update_page completely? +

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.

What MCP server provides confluence_update_page? +

confluence_update_page is provided by the Jira & Confluence MCP Server MCP server (katsuhirohonda/jira-confluence-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.