dev-module-list · Magento 2 Development MCP Server MCP

WHAT IT DOES

What dev-module-list does on Magento 2 Development MCP Server

AI agents call dev-module-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.

THE RISK

Low Risk

Why dev-module-list needs a policy

This tool retrieves information about installed modules and their status. It is a read-only operation that queries the system state without creating, modifying, deleting, or executing any actions. The verb 'list' and the passive nature of 'status' inspection confirm this is purely informational retrieval, placing it in the Read category with low severity.

From the tool's definition Tool name 'dev-module-list' and description 'List all Magento 2 modules and their status' indicate a query/retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access dev-module-list gives an agent:

POLICY

How to control dev-module-list

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-module-list:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dev-module-list": {}
  }
}

dev-module-list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Magento 2 Development MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Magento 2 Development MCP Server tools

Execute cache-clean Clear specific Magento 2 cache types or all caches Execute sys-cron-run Run Magento 2 cron jobs Execute cache-flush Flush specific Magento 2 cache types or all caches Execute db-query Execute SQL queries directly on Magento 2 database Execute setup-di-compile Compile Magento 2 dependency injection configuration Execute setup-static-content-deploy Deploy Magento 2 static content and assets Execute setup-upgrade Run Magento 2 setup upgrade to update database schema and data Write cache-disable Disable specific Magento 2 cache types

All 29 Magento 2 Development MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about dev-module-list

What does the dev-module-list tool do? +

List all Magento 2 modules and their status. It is categorised as a Read tool in the Magento 2 Development MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on dev-module-list? +

Register the Magento 2 Development MCP Server MCP server in PolicyLayer and add a rule for dev-module-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.

What risk level is dev-module-list? +

dev-module-list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit dev-module-list? +

Yes. Add a rate_limit block to the dev-module-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.

How do I block dev-module-list completely? +

Set action: deny in the PolicyLayer policy for dev-module-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.

What MCP server provides dev-module-list? +

dev-module-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.

Enforce policy on every Magento 2 Development MCP Server tool call.

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.

CHECK YOUR STACK →

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.