Get Magento 2 plugin (interceptor) list for a class across all scopes (global, adminhtml, frontend, crontab, webapi_rest, webapi_soap, graphql). When methodName is provided, analyzes that single method. When omitted, scans all public methods and reports only those with plugins.
AI agents call dev-plugin-list to retrieve information from Magento 2 Development MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reports information about Magento 2 plugins (interceptors) across different scopes. It performs read-only operations: listing plugins and analyzing method information. There are no side effects, no data is created, modified, or deleted, and no external operations are triggered.
From the tool's definition Tool description states it 'Get[s]... plugin list' and 'analyzes' or 'scans' methods to report plugins. The verb 'Get' combined with 'analyzes' and 'scans' indicates data retrieval and inspection with no mention of modification, deletion, or execution of code.
Documented attack patterns abuse exactly the kind of access dev-plugin-list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Magento 2 Development MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for dev-plugin-list:
{
"version": "1",
"default": "deny",
"tools": {
"dev-plugin-list": {}
}
}dev-plugin-list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get Magento 2 plugin (interceptor) list for a class across all scopes (global, adminhtml, frontend, crontab, webapi_rest, webapi_soap, graphql). When methodName is provided, analyzes that single method. When omitted, scans all public methods and reports only those with plugins. It is categorised as a Read tool in the Magento 2 Development MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Magento 2 Development MCP Server MCP server in PolicyLayer and add a rule for dev-plugin-list: 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 Magento 2 Development MCP Server. Nothing to install.
dev-plugin-list 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 dev-plugin-list 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 dev-plugin-list. 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.
dev-plugin-list is provided by the Magento 2 Development MCP Server MCP server (elgentos/magento2-dev-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Magento 2 Development MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
29 Magento 2 Development MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.