update_subscription

Update a subscription plan or billing

SERVERStripe SOURCE@modelcontextprotocol/server-stripe

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade D, identity verified Pull the record →

This record as markdown: /tools/stripe/update-subscription.md

WHAT IT DOES

What update_subscription does on Stripe

AI agents use update_subscription to commit financial operations through Stripe, usually the final step of a payment, billing, or trading workflow. A call moves real money.

RISK

Why update_subscription is rated Critical

Modifying a subscription directly affects recurring financial obligations: changing the plan, billing cycle, or pricing commits the customer (and merchant) to different ongoing charges. This is a financial operation with high blast radius if misused by an AI agent.

From the tool's definition update_subscription — 'Update a subscription plan or billing'

Risk signalsChanges subscription pricing or plan

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_subscription safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Stripe, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_subscription, this is the rule to start with:

update_subscription Approval-gated

Any call to update_subscription is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

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

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Stripe, apply this rule, and every update_subscription call is checked against it from then on.

FAQ

Questions about update_subscription

What does the update_subscription tool do? +

Update a subscription plan or billing. It is categorised as a Financial tool in the Stripe MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on update_subscription? +

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

What risk level is update_subscription? +

update_subscription 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 update_subscription? +

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

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

update_subscription is provided by the Stripe MCP server (@modelcontextprotocol/server-stripe). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Stripe, and thousands of servers like it.

This server

All 27 Stripe tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →