Check the status of AEM instance
AI agents call aem_status 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 tool retrieves status information about an AEM instance. It is a passive query operation with no side effects, data modification, code execution, or deletion capabilities. The blast radius of misuse is minimal—an agent could only gain visibility into system state, not cause harm or change anything.
From the tool's definition Tool name 'aem_status' and description 'Check the status of AEM instance' indicate a read-only operation that queries the state of the system without modifying any data or triggering side effects.
Attacks that exploit this kind of access
Check the status of AEM instance. 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_status: 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_status 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_status 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_status. 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_status 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 →