mittwald_container_recreate
Recreate a container.
This record as markdown: /tools/mittwald-mcp-server/mittwald-container-recreate.md
What mittwald_container_recreate does on Mittwald MCP Server
AI agents invoke mittwald_container_recreate to trigger actions in Mittwald 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 mittwald_container_recreate is rated High
Recreating a container is an Execute-level action: it stops the existing container instance and starts a new one, potentially causing downtime and side effects on running workloads. While not permanently destructive (data volumes typically persist), it triggers external operations with significant blast radius if misused on production containers.
From the tool's definition "Recreate a container" - recreating a container involves stopping and restarting it, which is an operational action that triggers external infrastructure changes
Attacks that exploit this kind of access
The rule that runs mittwald_container_recreate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mittwald MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mittwald_container_recreate, this is the rule to start with:
mittwald_container_recreate 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mittwald MCP Server, apply this rule, and every mittwald_container_recreate call is checked against it from then on.
Questions about mittwald_container_recreate
Recreate a container. It is categorised as a Execute tool in the Mittwald MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mittwald MCP Server MCP server in PolicyLayer and add a rule for mittwald_container_recreate: 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 Mittwald MCP Server. Nothing to install.
mittwald_container_recreate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the mittwald_container_recreate 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 mittwald_container_recreate. 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.
mittwald_container_recreate is provided by the Mittwald MCP Server MCP server (mittwald/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mittwald MCP Server, and thousands of servers like it.
Across the catalogue