wordpress_wc_get_coupons
AI agents call wordpress_wc_get_coupons 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.
The 'get' verb in the tool name indicates this retrieves coupon information from a WordPress WooCommerce store. No keywords suggesting creation, modification, deletion, or execution are present. The tool appears to query existing coupon data, which falls under the Read category. Confidence is reduced slightly due to the empty description, but the naming convention is sufficiently clear.
From the tool's definition Tool name 'wordpress_wc_get_coupons' contains 'get', indicating data retrieval. Description is empty, limiting direct confirmation, but the naming pattern (get_*) strongly suggests a retrieval operation without side effects.
Attacks that exploit this kind of access
wordpress_wc_get_coupons. It is categorised as a Read tool in the WordPress MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for wordpress_wc_get_coupons: 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.
wordpress_wc_get_coupons is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the wordpress_wc_get_coupons 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.
Set action: deny in the PolicyLayer policy for wordpress_wc_get_coupons. 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.
wordpress_wc_get_coupons is provided by the WordPress MCP Server MCP server (tonypepperwidow123-blip/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →