List direct child pages of a Confluence page, expanded with version, history and childTypes.page.
AI agents call confluence_get_page_children to retrieve information from Jira MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves hierarchical page structure information from Confluence. It performs no data modification, deletion, or external execution. The operation is a straightforward read that returns metadata about child pages (version, history, childTypes). No reversible or irreversible changes occur, and there are no financial implications.
From the tool's definition Tool name 'confluence_get_page_children' and description 'List direct child pages of a Confluence page' indicate a retrieval operation.
Attacks that exploit this kind of access
List direct child pages of a Confluence page, expanded with version, history and childTypes.page. It is categorised as a Read tool in the Jira MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Jira MCP Server 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 Jira MCP Server. 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 Jira MCP Server MCP server (rui-branco/jira-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 →