List installed packages in AEM
AI agents call aem_list_packages to retrieve information from AEM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure read operation that retrieves information about existing packages in the AEM system. It has no capability to create, modify, delete, or execute code. Even if an AI agent misuses this tool, it can only retrieve information that already exists, posing minimal security risk. The blast radius is confined to information disclosure, which is low severity in most contexts.
From the tool's definition Tool name 'aem_list_packages' and description 'List installed packages in AEM' indicate a retrieval operation with no side effects. It queries the state of installed packages without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
List installed packages in AEM. It is categorised as a Read tool in the AEM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AEM MCP Server MCP server in PolicyLayer and add a rule for aem_list_packages: 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.
aem_list_packages 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 aem_list_packages 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 aem_list_packages. 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.
aem_list_packages 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.
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 →