get_page
AI agents call get_page to retrieve information from MCP Atlassian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_page' tool follows the naming pattern of other retrieval-only tools on this server. No description is provided, but given the server's stated ability to 'search' Confluence pages and the consistent pattern of 'get_*' tools being read-only queries in this MCP server, this tool most likely retrieves page data from Confluence with no modifications or side effects. This is a low-severity Read operation.
From the tool's definition Tool name 'get_page' indicates a retrieval operation. Server description emphasizes 'search, create, and manage' capabilities, and sibling tools like 'get_issue', 'get_comments', 'get_labels', and 'download_attachments' are all Read operations retrieving data…
Attacks that exploit this kind of access
get_page. It is categorised as a Read tool in the MCP Atlassian MCP Server, which means it retrieves data without modifying state.
Register the MCP Atlassian MCP server in PolicyLayer and add a rule for 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 MCP Atlassian. Nothing to install.
get_page 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 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. 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 is provided by the MCP Atlassian MCP server (omkar9854/mcp-atlassian-onpremdc). 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 →