updateBillingEmail
Update the org's billing email. Validates format, writes private.organizations.billing_email, syncs to Stripe customer. Rate limit 30/h.
This record as markdown: /tools/io-stablebaseline-sb/updatebillingemail.md
What updateBillingEmail does on Stable Baseline
AI agents use updateBillingEmail to commit financial operations through Stable Baseline, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
email | string | Yes | |
organisation_id | string | Yes |
Parameters from the server's own tool schema.
Why updateBillingEmail is rated Critical
While updating an email address appears to be a Write operation, the explicit Stripe customer synchronization makes this a Financial category tool. Misuse could redirect billing communications, potentially enabling fraud or disrupting payment collection. The rate limit (30/h) and private data write further indicate sensitivity.
From the tool's definition 'syncs to Stripe customer' — modifying billing contact information on a payment processor (Stripe) constitutes a financial operation that could redirect invoices, affect payment flows, and disrupt billing relationships
Attacks that exploit this kind of access
The rule that runs updateBillingEmail safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stable Baseline, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For updateBillingEmail, this is the rule to start with:
Any call to updateBillingEmail is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Stable Baseline, apply this rule, and every updateBillingEmail call is checked against it from then on.
Questions about updateBillingEmail
Update the org's billing email. Validates format, writes private.organizations.billing_email, syncs to Stripe customer. Rate limit 30/h. It is categorised as a Financial tool in the Stable Baseline MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
updateBillingEmail accepts 2 parameters: email, organisation_id. Required: email, organisation_id. The full parameter table on this page comes from the server's own tool schema.
Register the Stable Baseline MCP server in PolicyLayer and add a rule for updateBillingEmail: 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 Stable Baseline. Nothing to install.
updateBillingEmail is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the updateBillingEmail 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 updateBillingEmail. 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.
updateBillingEmail is provided by the Stable Baseline MCP server (https://api.stablebaseline.io/functions/v1/cloud-serve/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stable Baseline, and thousands of servers like it.
Across the catalogue