// MCP TOOL REFERENCE

wpcs_full_check

ServerWPCS MCP Server
CategoryExecute

WHAT IT DOES

What wpcs_full_check does on WPCS MCP Server

AI agents invoke wpcs_full_check 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.

THE RISK

High Risk

Why wpcs_full_check needs a policy

This tool executes multiple static analysis and checking processes against WordPress code. It runs external tools (WPCS, PHPStan-style checks, compatibility scanners) and triggers analysis operations. It does not merely read data passively — it actively runs code analysis pipelines. No data is deleted or modified, and no financial transactions occur, so Execute is the most severe applicable category.

From the tool's definition 'Run comprehensive WordPress code check: WPCS + PHP Compatibility + Quality + Frontend + Code Analysis + Submission readiness'

Documented attack patterns abuse exactly the kind of access wpcs_full_check gives an agent:

POLICY

How to control wpcs_full_check

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_full_check:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wpcs_full_check": {
      "limits": [
        {
          "counter": "wpcs_full_check_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

wpcs_full_check 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.

Create a free account and register WPCS MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More WPCS MCP Server tools

Execute wpcs_pre_commit Pre-commit workflow optimized for WordPress plugins/themes: Auto-fix staged PHP files, re- Write wpcs_fix_file Auto-fix WordPress Coding Standards violations in a PHP file using phpcbf. Fixes spacing, Write wpcs_generate_report Generate a comprehensive report in JSON, Markdown, or summary format. Runs all enabled che Read wpcs_check_directory Check all PHP files in a directory against WordPress Coding Standards. Automatically exclu Read wpcs_check_file Check a single PHP file against WordPress Coding Standards. Read wpcs_check_php_compatibility Check PHP files for compatibility with specific PHP versions (8.1, 8.2, 8.3, 8.4). Uses PH Read wpcs_check_staged Check all staged PHP files against WordPress Coding Standards. Use this before committing Read wpcs_code_analysis Detect dead code and hook issues: unused/undefined functions, orphan callbacks, duplicate

All 14 WPCS MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in WPCS MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about wpcs_full_check

What does the wpcs_full_check tool do? +

Run comprehensive WordPress code check: WPCS + PHP Compatibility + Quality (security, performance, deprecated) + Frontend (accessibility, responsive) + Code Analysis (dead code, hooks) + Submission readiness. Use before release or WordPress.org submission. 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.

How do I enforce a policy on wpcs_full_check? +

Register the WPCS MCP Server MCP server in PolicyLayer and add a rule for wpcs_full_check: 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.

What risk level is wpcs_full_check? +

wpcs_full_check is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit wpcs_full_check? +

Yes. Add a rate_limit block to the wpcs_full_check 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.

How do I block wpcs_full_check completely? +

Set action: deny in the PolicyLayer policy for wpcs_full_check. 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.

What MCP server provides wpcs_full_check? +

wpcs_full_check 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.

Enforce policy on every WPCS MCP Server tool call.

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.

CHECK YOUR STACK →

Free to start. No card required.

14 WPCS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.