Perform security-focused validation on code. Checks for XSS vulnerabilities, SQL injection risks, insecure functions, and other security issues.
AI agents call check_security to retrieve information from Magento 2 Coding Standards MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a static analysis tool that retrieves or queries code properties to detect security patterns. It has no side effects: it does not execute code, modify data, delete anything, or trigger external operations. The input is code to be analyzed, and the output is a report of potential issues. This is a Read operation—security auditing through inspection rather than execution.
From the tool's definition Tool performs 'validation' and 'checks' on code—it analyzes and reports security issues without modifying, executing, or deleting any code or data.
Documented attack patterns abuse exactly the kind of access check_security 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 check_security:
{
"version": "1",
"default": "deny",
"tools": {
"check_security": {}
}
}check_security 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.
Perform security-focused validation on code. Checks for XSS vulnerabilities, SQL injection risks, insecure functions, and other security issues. It is categorised as a Read tool in the Magento 2 Coding Standards MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Magento 2 Coding Standards MCP Server MCP server in PolicyLayer and add a rule for check_security: 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.
check_security 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 check_security 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 check_security. 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.
check_security 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.