Get a Confluence page by its URL
AI agents call confluence_get_page_by_url to retrieve information from Atlassian 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 and queries Confluence page data with no side effects, modifications, or destructive operations. It matches the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch)'. The explicit 'read-only' designation of the parent server further confirms this classification.
From the tool's definition Tool name 'confluence_get_page_by_url' and description 'Get a Confluence page by its URL' indicate retrieval-only functionality. Server description explicitly states it is 'read-only MCP server' with 'retrieving content by ID or URL' as a capability.
Attacks that exploit this kind of access
Get a Confluence page by its URL. It is categorised as a Read tool in the Atlassian MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Atlassian MCP Server 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 Atlassian MCP Server. 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 Atlassian MCP Server MCP server (varunkumar/atlassian-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 →