upgrade_container

A execute tool on the 1Panel MCP server.

SERVER1Panel MCP Server SOURCEeaveluo/1panel-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/eaveluo-1panel-mcp/upgrade-container.md

What upgrade_container does on 1Panel MCP Server

AI agents invoke upgrade_container to trigger actions in 1Panel MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why upgrade_container is rated High

Upgrading a container involves stopping the current container, pulling a new image, and restarting it — this is an execution-level operation with potential side effects on running services. It is not purely destructive (data is not irreversibly deleted) but it does execute operations that can disrupt live workloads. Confidence is moderate due to the sparse description.

From the tool's definition Tool name 'upgrade_container' and description 'Upgrade container' indicate triggering an upgrade operation on a running Docker container, which executes an external operation affecting live infrastructure.

Questions about upgrade_container

What does the upgrade_container tool do? +

upgrade_container is a execute tool on the 1Panel MCP Server MCP server. It is categorised as a Execute tool in the 1Panel MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on upgrade_container? +

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

What risk level is upgrade_container? +

upgrade_container is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit upgrade_container? +

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

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

upgrade_container is provided by the 1Panel MCP Server MCP server (eaveluo/1panel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on 1Panel MCP Server, 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 1Panel MCP Server'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.