Replicate content to publish instance
AI agents invoke aem_replicate_content to trigger actions in AEM MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Replication triggers an external operation that pushes content from an author instance to a live publish instance, making it publicly visible. This is not a simple write (it crosses environment boundaries and has immediate external impact), nor is it purely destructive. It fits Execute because it triggers an external operation with broad effects depending on what content is replicated.
From the tool's definition Replicate content to publish instance
Attacks that exploit this kind of access
Replicate content to publish instance. It is categorised as a Execute tool in the AEM MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AEM MCP Server MCP server in PolicyLayer and add a rule for aem_replicate_content: 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_replicate_content is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the aem_replicate_content 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_replicate_content. 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_replicate_content 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 →