Get Confluence page content by specific code (like F4CjNw).
AI agents call query_wiki to retrieve information from Raalarcon Jira without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing Confluence wiki page content without altering, creating, or destroying any data. It is a straightforward read operation with minimal blast radius. A misuse would only expose information already accessible through normal Confluence access controls.
From the tool's definition Tool description states 'Get Confluence page content' — a retrieval operation with no modification, deletion, or execution capability. The parameter is a page code identifier.
Attacks that exploit this kind of access
Get Confluence page content by specific code (like F4CjNw). It is categorised as a Read tool in the Raalarcon Jira MCP Server, which means it retrieves data without modifying state.
Register the Raalarcon Jira MCP server in PolicyLayer and add a rule for query_wiki: 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 Raalarcon Jira. Nothing to install.
query_wiki 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 query_wiki 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 query_wiki. 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.
query_wiki is provided by the Raalarcon Jira MCP server (raalarcon-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 →