Detect dead code and hook issues: unused/undefined functions, orphan callbacks, duplicate definitions, hook priority conflicts, accepted_args mismatch, wrong-context hooks.
AI agents call wpcs_code_analysis 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 analyzes WordPress code statically to identify potential issues (dead code, hook problems) but does not execute code, modify files, delete data, or perform financial operations. It reads and reports on code quality metrics, making it a Read category tool. Severity is low because misuse would only result in incorrect analysis reports with no side effects on actual systems or data.
From the tool's definition Tool performs code analysis to 'detect' issues like unused functions, undefined functions, orphan callbacks, and hook conflicts. The description uses passive language (detect, identify) indicating inspection of code structure without modification.
Documented attack patterns abuse exactly the kind of access wpcs_code_analysis 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_code_analysis:
{
"version": "1",
"default": "deny",
"tools": {
"wpcs_code_analysis": {}
}
}wpcs_code_analysis 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.
Detect dead code and hook issues: unused/undefined functions, orphan callbacks, duplicate definitions, hook priority conflicts, accepted_args mismatch, wrong-context hooks. 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_code_analysis: 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_code_analysis 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_code_analysis 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_code_analysis. 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_code_analysis 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.