Get all content from a page including Experience Fragments and Content Fragments
AI agents call getPageContent 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 queries and retrieves existing page content without side effects. It does not create, modify, delete, or execute operations. The action is purely informational retrieval, which aligns with the Read category. The severity is low because retrieving content poses minimal risk unless the retrieved data itself is sensitive, but the tool's capability is fundamentally non-destructive and read-only.
From the tool's definition The tool name 'getPageContent' and description 'Get all content from a page including Experience Fragments and Content Fragments' indicate a retrieval operation with no modification, deletion, or execution of external processes.
Attacks that exploit this kind of access
Get all content from a page including Experience Fragments and Content Fragments. 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 getPageContent: 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.
getPageContent 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 getPageContent 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 getPageContent. 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.
getPageContent 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 →