Critical Risk →

commerce_refund

Request a refund for a commerce order.

Part of the Clawvault server.

commerce_refund can move real money through Clawvault, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE CLAWVAULT →

Free to start. No card required.

AI agents use commerce_refund to initiate financial transactions through Clawvault. Financial operations involve real money and are irreversible once processed. PolicyLayer blocks financial tools by default, requiring explicit human approval with transaction-level limits to prevent unauthorised spending.

commerce_refund moves real money. Without a policy, an autonomous agent could initiate transactions that drain accounts or exceed budgets. PolicyLayer blocks financial tools by default, requiring human-in-the-loop approval with configurable spending limits per transaction and per time window.

Financial tools involve real money. Block by default and require explicit human approval before enabling.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "commerce_refund": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

See the full Clawvault policy for all 45 tools.

Get this rule live on your own Clawvault server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY CLAWVAULT →

View all 45 tools →

These attack patterns abuse exactly the kind of access commerce_refund gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so commerce_refund only ever does what you allow.

SECURE CLAWVAULT →

Other financial tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the commerce_refund tool do? +

Request a refund for a commerce order.. It is categorised as a Financial tool in the Clawvault MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on commerce_refund? +

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

What risk level is commerce_refund? +

commerce_refund is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit commerce_refund? +

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

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

commerce_refund is provided by the Clawvault MCP server (clawvault-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 Clawvault tool call.

Deterministic rules across all 45 Clawvault tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.