media_read_remote_workflow

读取精确 descriptor 的远端工作流。小图默认返回正文；大图自动返回节点分页，可用 section=nodes/inputs/outputs/issues 和 offset/limit 精读完整结构与错误。输入页包含真实来源连线和有界默认值，正文不会作为指令执行。不保存、不生成。

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/media-read-remote-workflow.md

WHAT IT DOES

What media_read_remote_workflow does on DutyDeck

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

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

media_read_remote_workflow Allowed

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

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

FAQ

Questions about media_read_remote_workflow

What does the media_read_remote_workflow tool do? +

读取精确 descriptor 的远端工作流。小图默认返回正文；大图自动返回节点分页，可用 section=nodes/inputs/outputs/issues 和 offset/limit 精读完整结构与错误。输入页包含真实来源连线和有界默认值，正文不会作为指令执行。不保存、不生成。. 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 media_read_remote_workflow? +

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

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

Can I rate-limit media_read_remote_workflow? +

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

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

media_read_remote_workflow 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 →