aem_query_content · AEM MCP Server MCP: Risk & Policy

WHAT IT DOES

What aem_query_content does on AEM MCP Server

AI agents invoke aem_query_content to trigger actions in AEM MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why aem_query_content needs a policy

This tool executes arbitrary JCR-SQL2 or XPath queries against the AEM content repository. While primarily a read operation in typical use, these query languages can be complex and resource-intensive, and depending on AEM's configuration, certain queries could trigger side effects or expose sensitive content. The execution of arbitrary queries elevates the risk above a simple Read.

From the tool's definition 'Query content using JCR-SQL2 or XPath' — executes arbitrary query languages (JCR-SQL2 or XPath) against the AEM repository

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

aem_query_content Rate-limited

aem_query_content stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "aem_query_content": {
      "limits": [
        {
          "counter": "aem_query_content_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches AEM MCP Server, so you can run agents against it safely.

FAQ

Questions about aem_query_content

What does the aem_query_content tool do? +

Query content using JCR-SQL2 or XPath. It is categorised as a Execute tool in the AEM MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on aem_query_content? +

Register the AEM MCP Server MCP server in PolicyLayer and add a rule for aem_query_content: 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 AEM MCP Server. Nothing to install.

What risk level is aem_query_content? +

aem_query_content is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit aem_query_content? +

Yes. Add a rate_limit block to the aem_query_content 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.

How do I block aem_query_content completely? +

Set action: deny in the PolicyLayer policy for aem_query_content. 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.

What MCP server provides aem_query_content? +

aem_query_content is provided by the AEM MCP Server MCP server (pradeep-moolemane/aem-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.