server_docker_action

对指定的完整容器 ID 启动、停止或重启容器；每次都需要单独确认。执行前会再次核对容器身份并检查结果，结果不明确时不会自动重试。

SERVERDutyDeck SOURCEtaokoplay/DutyDeck

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dutydeck/server-docker-action.md

WHAT IT DOES

What server_docker_action does on DutyDeck

AI agents call server_docker_action to retrieve information from DutyDeck without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why server_docker_action is rated Low

Even though server_docker_action only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs server_docker_action safely

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

server_docker_action Allowed

server_docker_action is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "server_docker_action": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect DutyDeck, apply this rule, and every server_docker_action call is checked against it from then on.

FAQ

Questions about server_docker_action

What does the server_docker_action tool do? +

对指定的完整容器 ID 启动、停止或重启容器；每次都需要单独确认。执行前会再次核对容器身份并检查结果，结果不明确时不会自动重试。. It is categorised as a Read tool in the DutyDeck MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on server_docker_action? +

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

What risk level is server_docker_action? +

server_docker_action is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit server_docker_action? +

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

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

server_docker_action is provided by the DutyDeck MCP server (taokoplay/DutyDeck). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on DutyDeck, and thousands of servers like it.

This server

All 247 DutyDeck tools →

Across the catalogue

server_status on 010 Editor → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →