Create a new component on a page
AI agents use createComponent to create or update resources in AEM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AEM MCP Server environment.
Creating a new component on a page in AEM is a Write operation: it adds content to the system in a reversible manner (the component can be deleted or modified later). It does not execute arbitrary code, delete irreversibly, or involve financial transactions.
From the tool's definition Tool name is 'createComponent' and description states 'Create a new component on a page' — this is a creation operation that modifies content reversibly.
Attacks that exploit this kind of access
Create a new component on a page. It is categorised as a Write tool in the AEM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AEM MCP Server MCP server in PolicyLayer and add a rule for createComponent: 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.
createComponent is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the createComponent 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 createComponent. 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.
createComponent 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 →