Check all PHP files in a directory against WordPress Coding Standards. Automatically excludes vendor/, node_modules/, and build/ directories.
AI agents call wpcs_check_directory to retrieve information from WPCS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool scans PHP files to identify coding standard violations but does not execute code, modify files, delete data, or commit financial transactions. It is purely a linting/analysis operation that reports findings without side effects. The automatic exclusion of common directories further confirms it is a safe, read-only analysis tool.
From the tool's definition The tool performs checking and analysis ('check all PHP files') against WordPress Coding Standards with automatic exclusions. It retrieves or queries code quality issues with no modification, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access wpcs_check_directory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WPCS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for wpcs_check_directory:
{
"version": "1",
"default": "deny",
"tools": {
"wpcs_check_directory": {}
}
}wpcs_check_directory 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.
Check all PHP files in a directory against WordPress Coding Standards. Automatically excludes vendor/, node_modules/, and build/ directories. It is categorised as a Read tool in the WPCS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WPCS MCP Server MCP server in PolicyLayer and add a rule for wpcs_check_directory: 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 WPCS MCP Server. Nothing to install.
wpcs_check_directory 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 wpcs_check_directory 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 wpcs_check_directory. 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.
wpcs_check_directory is provided by the WPCS MCP Server MCP server (vapvarun/wpcs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WPCS 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.
14 WPCS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.