Create and register a new Magento 2 module
AI agents use dev-module-create to create or update resources in Magento 2 Development MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Magento 2 Development MCP Server environment.
The tool creates and registers module files/configurations, which modifies the codebase and system state but does not delete data, execute arbitrary code, or cause financial impact. This is a standard Write operation. Severity is medium because creating unintended modules could clutter the environment or introduce conflicts, but effects are reversible via deletion or deregistration.
From the tool's definition Tool description states 'Create and register a new Magento 2 module' — this creates new module artifacts and registers them in the system, which are reversible write operations on the development environment.
Documented attack patterns abuse exactly the kind of access dev-module-create 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-module-create:
{
"version": "1",
"default": "deny",
"tools": {
"dev-module-create": {
"limits": [
{
"counter": "dev-module-create_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}dev-module-create stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create and register a new Magento 2 module. It is categorised as a Write tool in the Magento 2 Development MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Magento 2 Development MCP Server MCP server in PolicyLayer and add a rule for dev-module-create: 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-module-create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the dev-module-create 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-module-create. 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-module-create 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.