WordPress.org pre-submission audit: GPL license, stable tag match, changelog version, no tracking without consent, dismissible notices, uninstall cleanup, ABSPATH guards, prefix checking, no CDN deps, trademark check, required files, SVN readiness.
AI agents call wpcs_submission_check 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 exclusively analyzes and validates WordPress plugin/theme submission requirements without modifying code, executing external commands, deleting data, or creating financial obligations. It examines file attributes, metadata compliance, and code patterns for audit purposes—a pure read/query operation with no side effects on the codebase or system state.
From the tool's definition Tool performs WordPress.org pre-submission audit checks including GPL license verification, stable tag matching, changelog validation, trademark checking, and SVN readiness assessment.
Documented attack patterns abuse exactly the kind of access wpcs_submission_check 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_submission_check:
{
"version": "1",
"default": "deny",
"tools": {
"wpcs_submission_check": {}
}
}wpcs_submission_check 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.
WordPress.org pre-submission audit: GPL license, stable tag match, changelog version, no tracking without consent, dismissible notices, uninstall cleanup, ABSPATH guards, prefix checking, no CDN deps, trademark check, required files, SVN readiness. 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_submission_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.
wpcs_submission_check 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_submission_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.
Set action: deny in the PolicyLayer policy for wpcs_submission_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.
wpcs_submission_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.
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.