restart_container

重启Docker容器

Server WeChat Official Account MCP Server jungley8/mcp4agent
Category Execute
Risk class High
Parameters 00 required

What restart_container does on WeChat Official Account MCP Server

AI agents invoke restart_container to trigger actions in WeChat Official Account 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 restart_container needs a policy

Restarting a container is an executable action that manipulates the state of external infrastructure. While not destructive (the container itself persists), it interrupts services and affects availability, making it Execute rather than Write. The severity is high because restarting a production container could disrupt WeChat Official Account services or other applications running in that environment.

From the tool's definition Tool name 'restart_container' with description '重启Docker容器' (restart Docker container). This directly restarts a running Docker container, triggering external operations whose effects depend on which container is targeted.

Questions about restart_container

What does the restart_container tool do? +

重启Docker容器. It is categorised as a Execute tool in the WeChat Official Account 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 restart_container? +

Register the WeChat Official Account MCP Server MCP server in PolicyLayer and add a rule for restart_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 WeChat Official Account MCP Server. Nothing to install.

What risk level is restart_container? +

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

Can I rate-limit restart_container? +

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

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

restart_container is provided by the WeChat Official Account MCP Server MCP server (jungley8/mcp4agent). 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.