List all accessible Confluence spaces (filtered by allowed spaces)
AI agents call list_spaces 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 performs a simple enumeration of Confluence spaces that the user has access to. It retrieves information without creating, modifying, deleting, or executing any operations. The read-only nature and limited blast radius (disclosure of available spaces only) make this a low-severity Read operation.
From the tool's definition Tool name 'list_spaces' and description 'List all accessible Confluence spaces' indicate a retrieval/query operation with no side effects. The description explicitly states it lists spaces without modifying or deleting anything.
Attacks that exploit this kind of access
List all accessible Confluence spaces (filtered by allowed spaces). 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 list_spaces: 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.
list_spaces 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 list_spaces 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 list_spaces. 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.
list_spaces is provided by the Confluence MCP Server MCP server (olson3r/confluence-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 →