server_task_read

读取当前会话任务的有界输出和真实退出状态。首次 offset=0，后续使用 nextOffset；waitMs 最多 30000，等待新输出或终态而无需 Bash sleep。exited 且 exitCode=0 才表示命令成功；unknown/interrupted 先核对远端实际状态，不能直接重试。

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-task-read.md

WHAT IT DOES

What server_task_read does on DutyDeck

AI agents call server_task_read 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_task_read is rated Low

Even though server_task_read 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_task_read 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_read, this is the rule to start with:

server_task_read Allowed

server_task_read 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_task_read": {}
  }
}

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_task_read call is checked against it from then on.

FAQ

Questions about server_task_read

What does the server_task_read tool do? +

读取当前会话任务的有界输出和真实退出状态。首次 offset=0，后续使用 nextOffset；waitMs 最多 30000，等待新输出或终态而无需 Bash sleep。exited 且 exitCode=0 才表示命令成功；unknown/interrupted 先核对远端实际状态，不能直接重试。. 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_task_read? +

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

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

Can I rate-limit server_task_read? +

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

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

server_task_read 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

binary_read on 010 Editor → The MCP Attack Database →

Guides

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