claudeus_wp_discover_endpoints

Discover available WordPress REST API endpoints

SERVERClaudeus WordPress MCP SOURCEdeus-h/claudeus-wp-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/deus-h-claudeus-wp-mcp/claudeus-wp-discover-endpoints.md

WHAT IT DOES

What claudeus_wp_discover_endpoints does on Claudeus WordPress MCP

AI agents call claudeus_wp_discover_endpoints to retrieve information from Claudeus WordPress MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why claudeus_wp_discover_endpoints is rated Low

This tool performs endpoint discovery/enumeration, which is a read-only operation. It queries available WordPress REST API endpoints to understand what capabilities are exposed, but does not invoke those endpoints, modify data, execute commands, or delete anything.

From the tool's definition Tool name and description indicate 'Discover available WordPress REST API endpoints' — a purely informational query operation that retrieves metadata about available API endpoints without modifying, executing code, or affecting data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs claudeus_wp_discover_endpoints 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_discover_endpoints, this is the rule to start with:

claudeus_wp_discover_endpoints Allowed

claudeus_wp_discover_endpoints is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "claudeus_wp_discover_endpoints": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claudeus WordPress MCP, apply this rule, and every claudeus_wp_discover_endpoints call is checked against it from then on.

FAQ

Questions about claudeus_wp_discover_endpoints

What does the claudeus_wp_discover_endpoints tool do? +

Discover available WordPress REST API endpoints. It is categorised as a Read tool in the Claudeus WordPress MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on claudeus_wp_discover_endpoints? +

Register the Claudeus WordPress MCP server in PolicyLayer and add a rule for claudeus_wp_discover_endpoints: 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.

What risk level is claudeus_wp_discover_endpoints? +

claudeus_wp_discover_endpoints is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit claudeus_wp_discover_endpoints? +

Yes. Add a rate_limit block to the claudeus_wp_discover_endpoints 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 claudeus_wp_discover_endpoints completely? +

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

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

KEEP EXPLORING

More on Claudeus WordPress, and thousands of servers like it.

This server

All 145 Claudeus WordPress tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →