set_container_state · Synology MCP Server MCP: Risk & Policy

WHAT IT DOES

What set_container_state does on Synology MCP Server

AI agents invoke set_container_state to trigger actions in Synology 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 IT NEEDS A POLICY

Why set_container_state needs a policy

This tool controls the runtime state of Docker containers — starting, stopping, or restarting them. These are external operational effects that can disrupt running services. It's not purely destructive (no data deletion) but executes state changes on infrastructure, potentially taking down services or triggering restarts with significant blast radius if misused.

From the tool's definition Start, stop or restart a Docker container. [control]

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_container_state Rate-limited

set_container_state 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": {
    "set_container_state": {
      "limits": [
        {
          "counter": "set_container_state_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Synology MCP Server, so you can run agents against it safely.

FAQ

Questions about set_container_state

What does the set_container_state tool do? +

Start, stop or restart a Docker container. [control]. It is categorised as a Execute tool in the Synology 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 set_container_state? +

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

What risk level is set_container_state? +

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

Can I rate-limit set_container_state? +

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

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

set_container_state is provided by the Synology MCP Server MCP server (rafalr100/synology-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.