Build a request to retrieve asset metadata from AEM Assets HTTP API.
AI agents call aem_metadata_get to retrieve information from Adobe Experience Assets Dev MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata from AEM Assets without side effects. It is a read-only query operation that does not create, modify, delete, or execute any external operations. The retrieval of asset metadata poses minimal security risk, as it only exposes information already stored in the system.
From the tool's definition Tool name contains 'get' and description states 'retrieve asset metadata' with no modification, deletion, or execution verbs.
Attacks that exploit this kind of access
Build a request to retrieve asset metadata from AEM Assets HTTP API. It is categorised as a Read tool in the Adobe Experience Assets Dev MCP MCP Server, which means it retrieves data without modifying state.
Register the Adobe Experience Assets Dev MCP server in PolicyLayer and add a rule for aem_metadata_get: 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 Adobe Experience Assets Dev MCP. Nothing to install.
aem_metadata_get 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_metadata_get 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_metadata_get. 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_metadata_get is provided by the Adobe Experience Assets Dev MCP server (stubbedev/adobe-experience-dev-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
aem_metadata_get is one line of Adobe Experience Assets Dev's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →