stripe_listen · Yaver MCP: Risk & Policy

WHAT IT DOES

What stripe_listen does on Yaver

AI agents invoke stripe_listen to trigger actions in Yaver. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

PARAMETERS

Parameter	Type	Required	Description
`path`	string	—	Webhook path (default /api/webhooks/stripe)
`port`	integer	—	Local port (default 3000)
`events`	array	—	Event filter (e.g. payment_intent.succeeded)

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why stripe_listen needs a policy

stripe_listen triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Risk signalsAccepts file system path (path)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stripe_listen Rate-limited

stripe_listen stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stripe_listen": {
      "limits": [
        {
          "counter": "stripe_listen_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Yaver, so you can run agents against it safely.

FAQ

Questions about stripe_listen

What does the stripe_listen tool do? +

Start Stripe webhook listener for local development. Forwards webhooks to localhost. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does stripe_listen accept? +

stripe_listen accepts 3 parameters: path, port, events. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on stripe_listen? +

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

What risk level is stripe_listen? +

stripe_listen is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit stripe_listen? +

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

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

stripe_listen is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.