Pre-commit workflow optimized for WordPress plugins/themes: Auto-fix staged PHP files, re-stage them, and report remaining issues. Automatically excludes vendor/, node_modules/, and build/ directories. Returns whether commit should proceed.
AI agents invoke wpcs_pre_commit to trigger actions in WPCS MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool performs multiple chained actions: it automatically modifies staged PHP files (write), re-stages them in git (execute/write to VCS state), and influences the commit workflow. Because it triggers external git operations and auto-modifies files without per-change approval, it falls under Execute.
From the tool's definition Auto-fix staged PHP files, re-stage them, and report remaining issues. Returns whether commit should proceed.
Documented attack patterns abuse exactly the kind of access wpcs_pre_commit 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_pre_commit:
{
"version": "1",
"default": "deny",
"tools": {
"wpcs_pre_commit": {
"limits": [
{
"counter": "wpcs_pre_commit_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}wpcs_pre_commit stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Pre-commit workflow optimized for WordPress plugins/themes: Auto-fix staged PHP files, re-stage them, and report remaining issues. Automatically excludes vendor/, node_modules/, and build/ directories. Returns whether commit should proceed. It is categorised as a Execute tool in the WPCS MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the WPCS MCP Server MCP server in PolicyLayer and add a rule for wpcs_pre_commit: 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_pre_commit is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the wpcs_pre_commit 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_pre_commit. 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_pre_commit 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.