media_save_local_workflow

新任务先检查服务器工作流，无匹配时根据实际模型和节点新建。authorizationMode=ask 时先取得用户同意并传 creationIntent=user-confirmed；automatic 时可直接新建并传 automatic-policy，Host 会复核当前设置。保存前校验真实节点接口、模型枚举、连线与输出；保存为本机跨项目复用模板，不提交生成。

SERVERDutyDeck SOURCEtaokoplay/DutyDeck

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dutydeck/media-save-local-workflow.md

WHAT IT DOES

What media_save_local_workflow does on DutyDeck

AI agents use media_save_local_workflow to create or update resources in DutyDeck, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DutyDeck environment.

RISK

Why media_save_local_workflow is rated Medium

An AI agent can call media_save_local_workflow faster than any human can review: one bad instruction and it creates or modifies resources in DutyDeck by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

media_save_local_workflow Rate-limited

media_save_local_workflow stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "media_save_local_workflow": {
      "limits": [
        {
          "counter": "media_save_local_workflow_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about media_save_local_workflow

What does the media_save_local_workflow tool do? +

How do I enforce a policy on media_save_local_workflow? +

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

media_save_local_workflow is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit media_save_local_workflow? +

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

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

media_save_local_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

save_snapshot on Why Did You Render → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →