upload_image_archive_and_redeploy_app

Rebuild flow for existing apps: upload a newly built image archive, push it with a new tag, keep the current slug, and redeploy the existing app.

Server PlugLayer MCP Server pluglayer/mcp
Category Execute
Risk class High
Parameters 00 required

What upload_image_archive_and_redeploy_app does on PlugLayer MCP Server

AI agents invoke upload_image_archive_and_redeploy_app to trigger actions in PlugLayer 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 upload_image_archive_and_redeploy_app needs a policy

This tool triggers a multi-step operation: uploading an image archive, pushing it to a registry with a new tag, and redeploying an existing application. The redeployment constitutes an external operation that affects running infrastructure.

From the tool's definition upload a newly built image archive, push it with a new tag, keep the current slug, and redeploy the existing app

Questions about upload_image_archive_and_redeploy_app

What does the upload_image_archive_and_redeploy_app tool do? +

Rebuild flow for existing apps: upload a newly built image archive, push it with a new tag, keep the current slug, and redeploy the existing app. It is categorised as a Execute tool in the PlugLayer 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 upload_image_archive_and_redeploy_app? +

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

What risk level is upload_image_archive_and_redeploy_app? +

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

Can I rate-limit upload_image_archive_and_redeploy_app? +

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

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

upload_image_archive_and_redeploy_app is provided by the PlugLayer MCP Server MCP server (pluglayer/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.