aem_install_package · AEM MCP Server MCP: Risk & Policy

WHAT IT DOES

What aem_install_package does on AEM MCP Server

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

Installing a package in AEM is an active execution operation that deploys content, OSGi bundles, scripts, and configurations into the running system. It can modify the system state in complex ways, potentially overwriting existing content or configurations.

From the tool's definition 'Install a package in AEM' — installing a package triggers execution of package contents, which may include scripts, configurations, content, and code deployments on the AEM instance

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

aem_install_package Rate-limited

aem_install_package 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_install_package": {
      "limits": [
        {
          "counter": "aem_install_package_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_install_package

What does the aem_install_package tool do? +

Install a package in AEM. 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_install_package? +

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

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

Can I rate-limit aem_install_package? +

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

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

aem_install_package 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.