mcp_get_debug_info

Get debug information: WordPress settings, server, database (name, prefix, charset), paths and debug constants

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/mcp-get-debug-info.md

WHAT IT DOES

What mcp_get_debug_info does on Wordpress

AI agents call mcp_get_debug_info 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 mcp_get_debug_info is rated Low

Retrieves sensitive configuration and debug information that could inform further attacks.

From the tool's definition WordPress settings, server, database name, prefix, charset, paths, debug constants

Attacks that exploit this kind of access

RECOMMENDED RULE

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

mcp_get_debug_info Allowed

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

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 mcp_get_debug_info call is checked against it from then on.

FAQ

Questions about mcp_get_debug_info

What does the mcp_get_debug_info tool do? +

Get debug information: WordPress settings, server, database (name, prefix, charset), paths and debug constants. 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 mcp_get_debug_info? +

Register the Wordpress MCP server in PolicyLayer and add a rule for mcp_get_debug_info: 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 mcp_get_debug_info? +

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

Can I rate-limit mcp_get_debug_info? +

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

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

mcp_get_debug_info 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 →