AI agents call get_kb_page_children to retrieve information from Jira 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 information about Confluence pages without side effects. It matches the Read category (retrieves or queries data; no side effects). The severity is low because exposure of page hierarchy information poses minimal risk—it provides navigation metadata rather than sensitive content access or destructive capabilities. High confidence due to clear read-only semantics.
From the tool's definition Tool retrieves child pages of a Confluence/KB page through 'Get' operation with no modification, deletion, or execution capability. Description emphasizes 'navigating page hierarchies' which is purely informational retrieval.
Attacks that exploit this kind of access
Get child pages of a Confluence/KB page. Useful for navigating page hierarchies. It is categorised as a Read tool in the Jira MCP Server, which means it retrieves data without modifying state.
Register the Jira MCP server in PolicyLayer and add a rule for get_kb_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. Nothing to install.
get_kb_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 get_kb_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 get_kb_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.
get_kb_page_children is provided by the Jira MCP server (taraskhust/jira-mcp-server). 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 →