Manage theme-specific coding standards. Themes layer additional rules on top of base Magento standards. Built-in presets: hyva (Alpine.js + TailwindCSS), luma (jQuery + RequireJS + LESS), breeze (Vanilla JS), porto (Luma-based + Porto widgets). Custom themes can be added as JSON files.
AI agents use manage_theme to create or update resources in Magento 2 Coding Standards MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Magento 2 Coding Standards MCP Server environment.
This tool creates or modifies theme configuration and standards (via JSON file uploads for custom themes), making it a Write operation. It does not execute arbitrary code, delete data irreversibly, or access financial systems.
From the tool's definition The tool description states 'Manage theme-specific coding standards' and 'Custom themes can be added as JSON files.' The word 'Manage' combined with the ability to add custom themes indicates creation and modification of configuration data.
Documented attack patterns abuse exactly the kind of access manage_theme gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Magento 2 Coding Standards MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for manage_theme:
{
"version": "1",
"default": "deny",
"tools": {
"manage_theme": {
"limits": [
{
"counter": "manage_theme_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}manage_theme 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.
Manage theme-specific coding standards. Themes layer additional rules on top of base Magento standards. Built-in presets: hyva (Alpine.js + TailwindCSS), luma (jQuery + RequireJS + LESS), breeze (Vanilla JS), porto (Luma-based + Porto widgets). Custom themes can be added as JSON files. It is categorised as a Write tool in the Magento 2 Coding Standards MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Magento 2 Coding Standards MCP Server MCP server in PolicyLayer and add a rule for manage_theme: 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 Coding Standards MCP Server. Nothing to install.
manage_theme 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 manage_theme 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 manage_theme. 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.
manage_theme is provided by the Magento 2 Coding Standards MCP Server MCP server (midhun-edv/magento-coding-standard-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Magento 2 Coding Standards 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.
7 Magento 2 Coding Standards MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.