wp_get_namespaces

List available REST API namespaces (plugins may add custom endpoints)

SERVERWordpress SOURCE@cavort-it-systems/wordpress-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/io-github-cvrt-jh-wordpress-mcp/wp-get-namespaces.md

WHAT IT DOES

What wp_get_namespaces does on Wordpress

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

RISK

Why wp_get_namespaces is rated Low

This tool performs passive discovery of REST API namespace information. It returns metadata about available endpoints and does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal — an attacker gains only informational insight into what APIs are available, which is typically non-sensitive discovery data.

From the tool's definition Tool description states 'List available REST API namespaces' — a read-only operation that retrieves and enumerates available endpoints without modifying or executing anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs wp_get_namespaces safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Wordpress, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wp_get_namespaces, this is the rule to start with:

wp_get_namespaces Allowed

wp_get_namespaces 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": {
    "wp_get_namespaces": {}
  }
}

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

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

FAQ

Questions about wp_get_namespaces

What does the wp_get_namespaces tool do? +

List available REST API namespaces (plugins may add custom endpoints). It is categorised as a Read tool in the Wordpress MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on wp_get_namespaces? +

Register the Wordpress MCP server in PolicyLayer and add a rule for wp_get_namespaces: 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. Nothing to install.

What risk level is wp_get_namespaces? +

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

Can I rate-limit wp_get_namespaces? +

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

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

wp_get_namespaces is provided by the Wordpress MCP server (@cavort-it-systems/wordpress-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Wordpress, and thousands of servers like it.

This server

All 314 Wordpress tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

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