Low Risk

wordpress_list_shortcodes

wordpress_list_shortcodes

How to control wordpress_list_shortcodes ↓

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

Low Risk

This tool retrieves or queries existing WordPress shortcodes without creating, modifying, or deleting them. It has no side effects and presents minimal risk if an AI agent invokes it. The 'list_' prefix is a standard convention for read operations that enumerate resources.

From the tool's definition Tool name 'wordpress_list_shortcodes' indicates a listing/query operation. The suffix 'list_' combined with 'shortcodes' suggests retrieval of shortcode data with no modification. Description is empty but the name strongly implies read-only enumeration.

Documented attack patterns abuse exactly the kind of access wordpress_list_shortcodes gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and WordPress MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for wordpress_list_shortcodes:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "wordpress_list_shortcodes": {}
  }
}

wordpress_list_shortcodes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register WordPress MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the wordpress_list_shortcodes tool do? +

wordpress_list_shortcodes. It is categorised as a Read tool in the WordPress MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on wordpress_list_shortcodes? +

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

What risk level is wordpress_list_shortcodes? +

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

Can I rate-limit wordpress_list_shortcodes? +

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

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

wordpress_list_shortcodes is provided by the WordPress MCP Server MCP server (raheesahmed/wordpress-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every WordPress MCP Server tool call.

Deterministic rules across all 190 WordPress MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

190 WordPress MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.