Get a page with its body content.
AI agents call get_page_with_body to retrieve information from Confluence MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves page content from Confluence with no side effects. It is a read-only operation that queries and returns data. While the server includes destructive tools (delete_page) and write tools (create_page, update_page), this specific tool performs only data retrieval, making it the least severe category.
From the tool's definition Tool name 'get_page_with_body' and description 'Get a page with its body content' indicate retrieval of existing data without modification. No creation, deletion, update, or execution operations are performed.
Attacks that exploit this kind of access
Get a page with its body content. It is categorised as a Read tool in the Confluence MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Confluence MCP Server MCP server in PolicyLayer and add a rule for get_page_with_body: 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 MCP Server. Nothing to install.
get_page_with_body is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_page_with_body 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 get_page_with_body. 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.
get_page_with_body is provided by the Confluence MCP Server MCP server (masna-ai/mcp-confluence-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →