Low Risk

wordpress_wc_get_top_sellers

wordpress_wc_get_top_sellers

How to control wordpress_wc_get_top_sellers ↓

AI agents call wordpress_wc_get_top_sellers 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 sales data (top-selling products) from a WooCommerce store without modifying, deleting, or executing operations. Read operations on commercial data carry low risk unless the data is highly sensitive; typical e-commerce sales analytics have minimal blast radius.

From the tool's definition Tool name 'wordpress_wc_get_top_sellers' indicates a retrieval operation ('get') on WooCommerce data. The naming pattern aligns with query/read operations. Description is empty, but the semantic intent is clear from the name.

Documented attack patterns abuse exactly the kind of access wordpress_wc_get_top_sellers 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_wc_get_top_sellers:

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

wordpress_wc_get_top_sellers 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_wc_get_top_sellers tool do? +

wordpress_wc_get_top_sellers. 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_wc_get_top_sellers? +

Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for wordpress_wc_get_top_sellers: 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_wc_get_top_sellers? +

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

Can I rate-limit wordpress_wc_get_top_sellers? +

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

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

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