List available AEM Assets integration categories and whether each is currently loaded.
AI agents call list_categories 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 queries configuration or status information (which categories are loaded) without creating, modifying, deleting, or executing any operations. It is a read-only informational tool with minimal security risk.
From the tool's definition Tool name 'list_categories' and description 'List available AEM Assets integration categories and whether each is currently loaded' indicate retrieval of metadata about available categories with no modification or execution of operations.
Attacks that exploit this kind of access
List available AEM Assets integration categories and whether each is currently loaded. 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 list_categories: 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.
list_categories 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 list_categories 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 list_categories. 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.
list_categories 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 →