Explain authentication and headers commonly required for AEM Assets API integrations.
AI agents call aem_explain_auth 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 and provides explanatory information about authentication requirements and API headers. It has no side effects, does not execute code or commands, does not create, modify, or delete data. The worst-case misuse scenario is providing incorrect or misleading authentication guidance, which is a low-severity informational risk. It belongs in the Read category as a reference/documentation tool.
From the tool's definition Tool name and description: 'aem_explain_auth' and 'Explain authentication and headers commonly required for AEM Assets API integrations.' The verb 'Explain' indicates information retrieval and documentation of authentication patterns, not modification,…
Attacks that exploit this kind of access
Explain authentication and headers commonly required for AEM Assets API integrations. 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_explain_auth: 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_explain_auth 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_explain_auth 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_explain_auth. 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_explain_auth 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.
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 →