List pages in a Confluence space. Returns page titles, IDs, and metadata.
AI agents call confluence_list_pages to retrieve information from Atlassian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns data (page titles, IDs, metadata) from a Confluence space with no side effects. It performs a read-only operation typical of list/fetch operations. The blast radius is minimal—an agent misusing this tool would only retrieve information already visible to the authenticated user.
From the tool's definition Tool name 'confluence_list_pages' and description 'List pages in a Confluence space. Returns page titles, IDs, and metadata' indicate retrieval of information without modification or execution.
Documented attack patterns abuse exactly the kind of access confluence_list_pages gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Atlassian, and nothing reaches the server without passing your rules. This is the rule we recommend for confluence_list_pages:
{
"version": "1",
"default": "deny",
"tools": {
"confluence_list_pages": {}
}
}confluence_list_pages is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List pages in a Confluence space. Returns page titles, IDs, and metadata. It is categorised as a Read tool in the Atlassian MCP Server, which means it retrieves data without modifying state.
Register the Atlassian MCP server in PolicyLayer and add a rule for confluence_list_pages: 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. Nothing to install.
confluence_list_pages 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_list_pages 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_list_pages. 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_list_pages is provided by the Atlassian MCP server (xuanxt/atlassian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Atlassian, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
51 Atlassian tools catalogued and risk-classified — across an index of 43,000+ MCP servers.