push_image

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/push-image.md

WHAT IT DOES

What push_image does on 1Panel MCP Server

AI agents invoke push_image 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.

RISK

Why push_image is rated High

Pushing a Docker image sends data to an external container registry. This is an external operation with side effects beyond local state changes, classifying it as Execute. The severity is medium as a misused push could expose proprietary images or overwrite existing registry tags, but it doesn't directly destroy data or move money.

From the tool's definition 'Push image' - pushing a Docker image to a registry triggers an external operation (network upload to a remote registry)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs push_image safely

PolicyLayer is an MCP gateway: it sits between your AI agents and 1Panel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For push_image, this is the rule to start with:

push_image Rate-limited

push_image stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "push_image": {
      "limits": [
        {
          "counter": "push_image_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 1Panel MCP Server, apply this rule, and every push_image call is checked against it from then on.

FAQ

Questions about push_image

What does the push_image tool do? +

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

Register the 1Panel MCP Server MCP server in PolicyLayer and add a rule for push_image: 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 push_image? +

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

Can I rate-limit push_image? +

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

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

push_image 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.

KEEP EXPLORING

More on 1Panel MCP Server, and thousands of servers like it.

This server

All 286 1Panel MCP Server tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →