Low Risk

confluence_get_page

Get full content of a Confluence page by ID. Returns title, body content, status, version, and space info.

Part of the Confluence server.

confluence_get_page is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE CONFLUENCE →

Free to start. No card required.

AI agents call confluence_get_page to retrieve information from Confluence without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though confluence_get_page only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "confluence_get_page": {}
  }
}

See the full Confluence policy for all 25 tools.

Get this rule live on your own Confluence server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY CONFLUENCE →

View all 25 tools →

These attack patterns abuse exactly the kind of access confluence_get_page gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so confluence_get_page only ever does what you allow.

SECURE CONFLUENCE →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the confluence_get_page tool do? +

Get full content of a Confluence page by ID. Returns title, body content, status, version, and space info.. It is categorised as a Read tool in the Confluence MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on confluence_get_page? +

Register the Confluence MCP server in PolicyLayer and add a rule for confluence_get_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 Confluence. Nothing to install.

What risk level is confluence_get_page? +

confluence_get_page is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit confluence_get_page? +

Yes. Add a rate_limit block to the confluence_get_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_get_page completely? +

Set action: deny in the PolicyLayer policy for confluence_get_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_get_page? +

confluence_get_page is provided by the Confluence MCP server (https://gateway.pipeworx.io/confluence/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Confluence tool call.

Deterministic rules across all 25 Confluence tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.