Get child pages of a specific page. Returns a list of direct children.
AI agents call confluence_get_page_children 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 retrieves hierarchical page structure information from Confluence without modifying any data. It is a straightforward query operation that lists child pages beneath a parent page, fitting the Read category perfectly. The blast radius is minimal since retrieval alone poses no risk of data loss or unauthorized modifications.
From the tool's definition Tool name contains 'get' and description states 'Get child pages' and 'Returns a list of direct children' - these indicate data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access confluence_get_page_children 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_get_page_children:
{
"version": "1",
"default": "deny",
"tools": {
"confluence_get_page_children": {}
}
}confluence_get_page_children 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.
Get child pages of a specific page. Returns a list of direct children. 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_get_page_children: 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_get_page_children 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_children 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_children. 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_children 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.