check_wordpress_site
Detect whether a site runs WordPress and assess its security posture. Checks: WP generator meta tag, wp-content/wp-includes paths, WP REST API (/wp-json/), login page (/wp-login.php), XML-RPC (/xmlrpc.php), active theme, and visible plugins. Returns WordPress detection confidence, theme info, plu...
This record as markdown: /tools/io-github-homenshum-nodebench/check-wordpress-site.md
What check_wordpress_site does on Nodebench
AI agents call check_wordpress_site to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_wordpress_site is rated Low
The tool performs reconnaissance and security assessment through HTTP checks and response analysis. It retrieves and queries information about a WordPress site's configuration and exposed components without altering any data or executing commands on the target server. This is purely informational/diagnostic activity with no side effects, fitting the Read category.
From the tool's definition Detects WordPress presence and assesses security posture by checking meta tags, file paths, REST API availability, login pages, and visible plugins. No modification, deletion, execution, or financial operations described.
Attacks that exploit this kind of access
The rule that runs check_wordpress_site safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_wordpress_site, this is the rule to start with:
check_wordpress_site is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every check_wordpress_site call is checked against it from then on.
Questions about check_wordpress_site
Detect whether a site runs WordPress and assess its security posture. Checks: WP generator meta tag, wp-content/wp-includes paths, WP REST API (/wp-json/), login page (/wp-login.php), XML-RPC (/xmlrpc.php), active theme, and visible plugins. Returns WordPress detection confidence, theme info, plugin list, and security score with risk assessments. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for check_wordpress_site: 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 Nodebench. Nothing to install.
check_wordpress_site 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 check_wordpress_site 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 check_wordpress_site. 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.
check_wordpress_site is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue