claudeus_wp_health__test_loopback
Test loopback requests. Verify that the site can make HTTP requests to itself (required for WP-Cron and other features).
This record as markdown: /tools/deus-h-claudeus-wp-mcp/claudeus-wp-health--test-loopback.md
What claudeus_wp_health__test_loopback does on Claudeus WordPress MCP
AI agents invoke claudeus_wp_health__test_loopback to trigger actions in Claudeus WordPress MCP. 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.
Why claudeus_wp_health__test_loopback is rated High
This tool triggers an HTTP request from the WordPress site back to itself, which is an active operation with external side effects (network request). It doesn't merely read stored data — it executes a loopback test. However, the blast radius is low as it's a diagnostic/verification operation with no data modification or deletion.
From the tool's definition Test loopback requests. Verify that the site can make HTTP requests to itself
Attacks that exploit this kind of access
The rule that runs claudeus_wp_health__test_loopback safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claudeus WordPress MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For claudeus_wp_health__test_loopback, this is the rule to start with:
claudeus_wp_health__test_loopback 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Claudeus WordPress MCP, apply this rule, and every claudeus_wp_health__test_loopback call is checked against it from then on.
Questions about claudeus_wp_health__test_loopback
Test loopback requests. Verify that the site can make HTTP requests to itself (required for WP-Cron and other features). It is categorised as a Execute tool in the Claudeus WordPress MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claudeus WordPress MCP server in PolicyLayer and add a rule for claudeus_wp_health__test_loopback: 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 Claudeus WordPress MCP. Nothing to install.
claudeus_wp_health__test_loopback is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the claudeus_wp_health__test_loopback 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 claudeus_wp_health__test_loopback. 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.
claudeus_wp_health__test_loopback is provided by the Claudeus WordPress MCP server (deus-h/claudeus-wp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claudeus WordPress, and thousands of servers like it.
Across the catalogue