media_wait_generation

等待统一媒体任务 revision 变化或终态；超时只返回当前快照，不取消远端任务。

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/media-wait-generation.md

WHAT IT DOES

What media_wait_generation does on DutyDeck

AI agents invoke media_wait_generation 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 media_wait_generation is rated High

media_wait_generation 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 media_wait_generation 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_wait_generation, this is the rule to start with:

media_wait_generation Rate-limited

media_wait_generation 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": {
    "media_wait_generation": {
      "limits": [
        {
          "counter": "media_wait_generation_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 media_wait_generation call is checked against it from then on.

FAQ

Questions about media_wait_generation

What does the media_wait_generation tool do? +

等待统一媒体任务 revision 变化或终态；超时只返回当前快照，不取消远端任务。. 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 media_wait_generation? +

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

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

Can I rate-limit media_wait_generation? +

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

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

media_wait_generation 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

browser_wait_for_element on Percepta MCP Server →wait_for_renders on Why Did You Render →qt_wait_for on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

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