Update a rate plan charge on a subscription. PUT /subscriptions/{subscriptionId}/rateplan-charges/{chargeId}. Required: subscriptionId, chargeId, quantity, name, chargeModel (flatFeePricing|perUnitPricing|tieredPricing|volumePricing), billCycleType, chargeTier (array: currency, price required). F...
AI agents use update_subscription_rate_plan_charge to create or update resources in Rebillia MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rebillia MCP Server environment.
This tool modifies an existing subscription rate plan charge via a PUT request, changing billing parameters like quantity, price, and charge model. While reversible in principle (values can be updated again), misuse could alter customer billing amounts, making it high severity. It does not move money directly, so Financial is not warranted, but Write is appropriate as it modifies billing configuration data.
From the tool's definition Update a rate plan charge on a subscription. PUT /subscriptions/{subscriptionId}/rateplan-charges/{chargeId}
Attacks that exploit this kind of access
Update a rate plan charge on a subscription. PUT /subscriptions/{subscriptionId}/rateplan-charges/{chargeId}. Required: subscriptionId, chargeId, quantity, name, chargeModel (flatFeePricing|perUnitPricing|tieredPricing|volumePricing), billCycleType, chargeTier (array: currency, price required). For price, you can pass a string dollars. It is categorised as a Write tool in the Rebillia MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rebillia MCP Server MCP server in PolicyLayer and add a rule for update_subscription_rate_plan_charge: 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 Rebillia MCP Server. Nothing to install.
update_subscription_rate_plan_charge is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_subscription_rate_plan_charge 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 update_subscription_rate_plan_charge. 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.
update_subscription_rate_plan_charge is provided by the Rebillia MCP Server MCP server (rhinosaas/rebillia-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →