Get all available sites in AEM
AI agents call fetchSites 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 performs a query/fetch operation that retrieves existing site information from AEM without creating, modifying, deleting, or executing any code. It is a read-only operation with minimal blast radius if misused by an AI agent—the worst outcome would be exposure of site names/metadata, not data destruction or unauthorized actions.
From the tool's definition Tool name 'fetchSites' and description 'Get all available sites in AEM' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Get all available sites 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 fetchSites: 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.
fetchSites 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 fetchSites 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 fetchSites. 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.
fetchSites 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.
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 →