This record as markdown: /tools/hermoso/upgrade-plan.md
What upgrade_plan does on Hermoso
AI agents use upgrade_plan to commit financial operations through Hermoso, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why upgrade_plan is rated Critical
Despite the minimal description, the tool name 'upgrade_plan' combined with the server's commercial context (ad generation SaaS with billing tools) strongly implies this changes a subscription tier, incurring recurring financial commitments. Sibling tools 'billing_status' and 'buy_credits' confirm a financial system is present. Upgrading a plan is a Financial action as it commits the account to recurring charges.
From the tool's definition 'upgrade_plan' and 'Change this account' — in the context of a billing/subscription platform (sibling tools include 'billing_status' and 'buy_credits'), upgrading a plan commits financial obligations
Attacks that exploit this kind of access
The rule that runs upgrade_plan safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hermoso, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For upgrade_plan, this is the rule to start with:
Any call to upgrade_plan is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Hermoso, apply this rule, and every upgrade_plan call is checked against it from then on.
Questions about upgrade_plan
Change this account. It is categorised as a Financial tool in the Hermoso MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Hermoso MCP server in PolicyLayer and add a rule for upgrade_plan: 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 Hermoso. Nothing to install.
upgrade_plan 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 upgrade_plan 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 upgrade_plan. 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.
upgrade_plan is provided by the Hermoso MCP server (https://app.hermoso.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hermoso, and thousands of servers like it.
Across the catalogue