Fetch a Confluence page by URL with footer and inline comments (including nested replies).
AI agents call confluence_get_page_by_url to retrieve information from Work Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries and retrieves existing Confluence page data. No data is created, modified, deleted, or executed. The tool merely fetches and returns information, making it a straightforward Read category with low severity.
From the tool's definition Tool name 'confluence_get_page_by_url' and description 'Fetch a Confluence page' — retrieves data without modification. Returns page content and comments with no side effects.
Attacks that exploit this kind of access
Fetch a Confluence page by URL with footer and inline comments (including nested replies). It is categorised as a Read tool in the Work Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Work Integrations MCP server in PolicyLayer and add a rule for confluence_get_page_by_url: 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 Work Integrations MCP. Nothing to install.
confluence_get_page_by_url 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 confluence_get_page_by_url 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_get_page_by_url. 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_get_page_by_url is provided by the Work Integrations MCP server (nazarky/workspace-mcp). 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 →