confluence_update_page · Jira MCP Server MCP: Risk & Policy

WHAT IT DOES

What confluence_update_page does on Jira MCP Server

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

WHY IT NEEDS A POLICY

Why confluence_update_page needs a policy

confluence_update_page modifies existing content by updating page title and body in Confluence. This is a Write operation because it creates or modifies data reversibly—the changes can be undone via version history or subsequent updates. It does not delete data (which would be Destructive), execute arbitrary code (Execute), or move money (Financial).

From the tool's definition Tool description explicitly states 'Update an existing Confluence page' with modifications to 'Title and/or body'. This is a reversible modification operation.

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 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. Title and/or body (storage XHTML). Version auto-bumps if omitted (fetches current version first). Confluence requires version.number = current + 1. It is categorised as a Write tool in the Jira 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 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 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 MCP Server MCP server (rui-branco/jira-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.