Check PHP files for compatibility with specific PHP versions (8.1, 8.2, 8.3, 8.4). Uses PHPCompatibilityWP to detect deprecated functions, removed features, and syntax incompatibilities. Essential for ensuring your plugin/theme works across PHP versions.
AI agents call wpcs_check_php_compatibility 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 reads and analyzes PHP files using PHPCompatibilityWP to generate compatibility reports. It retrieves information about code quality issues without creating, modifying, executing, or deleting any data. The analysis is purely informational, making this a Read operation with low severity—misuse would at worst produce false positives in a report, with no side effects on the codebase.
From the tool's definition Tool performs static analysis and checking: 'Check PHP files for compatibility', 'detect deprecated functions, removed features, and syntax incompatibilities'. No modification, execution, or deletion of files occurs. The verb is 'check' (analysis only).
Documented attack patterns abuse exactly the kind of access wpcs_check_php_compatibility 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_php_compatibility:
{
"version": "1",
"default": "deny",
"tools": {
"wpcs_check_php_compatibility": {}
}
}wpcs_check_php_compatibility 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 PHP files for compatibility with specific PHP versions (8.1, 8.2, 8.3, 8.4). Uses PHPCompatibilityWP to detect deprecated functions, removed features, and syntax incompatibilities. Essential for ensuring your plugin/theme works across PHP versions. 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_php_compatibility: 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_php_compatibility 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_php_compatibility 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_php_compatibility. 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_php_compatibility 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.