stripe_list_refunds

Recent Stripe refunds: id, amount, currency, status, created, charge, reason, WooCommerce order_id. Read-only; refunds are not created here.

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/stripe-list-refunds.md

WHAT IT DOES

What stripe_list_refunds does on Wordpress

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

Accesses sensitive financial transaction refund records but no write or financial commitment capability.

From the tool's definition Recent Stripe refunds, read-only, refunds not created

Attacks that exploit this kind of access

RECOMMENDED RULE

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

stripe_list_refunds Allowed

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

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

FAQ

Questions about stripe_list_refunds

What does the stripe_list_refunds tool do? +

Recent Stripe refunds: id, amount, currency, status, created, charge, reason, WooCommerce order_id. Read-only; refunds are not created here. 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 stripe_list_refunds? +

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

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

Can I rate-limit stripe_list_refunds? +

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

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

stripe_list_refunds 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

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

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