server_task_start

复用运维模块已连接的 SSH，在独立可见终端中执行发布或需要 sudo 交互的命令。每次启动都要单独确认；不受短命令 120 秒上限限制。密码只能由用户在运维任务终端输入，禁止写入命令或聊天。返回任务身份不代表执行成功。

SERVERDutyDeck SOURCEtaokoplay/DutyDeck

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dutydeck/server-task-start.md

WHAT IT DOES

What server_task_start does on DutyDeck

AI agents invoke server_task_start to trigger actions in DutyDeck. 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.

RISK

Why server_task_start is rated High

server_task_start triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs server_task_start 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_task_start, this is the rule to start with:

server_task_start Rate-limited

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

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about server_task_start

What does the server_task_start tool do? +

复用运维模块已连接的 SSH，在独立可见终端中执行发布或需要 sudo 交互的命令。每次启动都要单独确认；不受短命令 120 秒上限限制。密码只能由用户在运维任务终端输入，禁止写入命令或聊天。返回任务身份不代表执行成功。. It is categorised as a Execute tool in the DutyDeck MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on server_task_start? +

Register the DutyDeck MCP server in PolicyLayer and add a rule for server_task_start: 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_task_start? +

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

Can I rate-limit server_task_start? +

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

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

server_task_start 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 → High-risk tools on this server →

Across the catalogue

start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →