New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

upgrade_plan

Change this account

SERVERHermoso SOURCEhttps://app.hermoso.ai/mcp
Critical RISK CLASS
Category Financial
Parameters 00 required
Recommended Approval-gatedsee the rule below
Registry record Grade D, identity unverified Pull the record →

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

Questions about upgrade_plan

What does the upgrade_plan tool do? +

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.

How do I enforce a policy on upgrade_plan? +

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.

What risk level is upgrade_plan? +

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

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.

How do I block upgrade_plan completely? +

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.

What MCP server provides upgrade_plan? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Hermoso's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.