executeJCRQuery · AEM MCP Server MCP: Risk & Policy

WHAT IT DOES

What executeJCRQuery does on AEM MCP Server

AI agents invoke executeJCRQuery 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 executeJCRQuery needs a policy

JCR (Java Content Repository) query execution is a code/query execution operation where the effects depend entirely on the query content provided. While JCR queries themselves are typically read-only by default, the tool permits arbitrary query execution which could be crafted to cause unintended side effects or access sensitive data across the repository.

From the tool's definition Tool name 'executeJCRQuery' and description 'Execute JCR query' indicate execution of queries against the Java Content Repository. JCR queries can be arbitrary and potentially complex, making this an Execute operation rather than a simple Read.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

executeJCRQuery Rate-limited

executeJCRQuery 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": {
    "executeJCRQuery": {
      "limits": [
        {
          "counter": "executejcrquery_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 executeJCRQuery

What does the executeJCRQuery tool do? +

Execute JCR query. 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 executeJCRQuery? +

Register the AEM MCP Server MCP server in PolicyLayer and add a rule for executeJCRQuery: 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 executeJCRQuery? +

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

Can I rate-limit executeJCRQuery? +

Yes. Add a rate_limit block to the executeJCRQuery 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 executeJCRQuery completely? +

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

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