wordpress_verify_core_files
AI agents call wordpress_verify_core_files to retrieve information from WordPress MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Verification operations are non-destructive reads that query file integrity without making changes. However, confidence is moderate (0.7) rather than high because the description is empty, leaving some ambiguity about whether verification might trigger unexpected side effects or remediation actions. The name itself strongly suggests a Read operation—checking WordPress core files against their known state.
From the tool's definition Tool name 'wordpress_verify_core_files' indicates a verification/integrity check operation. The word 'verify' typically implies reading and comparing file checksums or metadata against known values, with no modification of files.
Attacks that exploit this kind of access
wordpress_verify_core_files. It is categorised as a Read tool in the WordPress MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for wordpress_verify_core_files: 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 WordPress MCP Server. Nothing to install.
wordpress_verify_core_files 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 wordpress_verify_core_files 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 wordpress_verify_core_files. 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.
wordpress_verify_core_files is provided by the WordPress MCP Server MCP server (tonypepperwidow123-blip/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →