remove_silence · Descript Complete MCP: Risk & Policy

WHAT IT DOES

What remove_silence does on Descript Complete

AI agents invoke remove_silence to trigger actions in Descript Complete. 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.

WHY IT NEEDS A POLICY

Why remove_silence needs a policy

This tool triggers an AI agent to perform automated audio/video editing (removing silence) on a project. It is an external operation whose effects depend on the project argument. While it modifies the project, it is more of an AI-executed processing action than a simple write. The modification could be difficult to reverse depending on Descript's versioning, but it is not explicitly irreversible/destructive.

From the tool's definition 'remove silent gaps from a project' using 'Descript AI agent' — triggers an automated AI-driven operation that modifies project content by removing silence segments

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

remove_silence Rate-limited

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Descript Complete, so you can run agents against it safely.

FAQ

Questions about remove_silence

What does the remove_silence tool do? +

Use the Descript AI agent to remove silent gaps from a project. Example: remove_silence({ project_id:. It is categorised as a Execute tool in the Descript Complete MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on remove_silence? +

Register the Descript Complete MCP server in PolicyLayer and add a rule for remove_silence: 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 Descript Complete. Nothing to install.

What risk level is remove_silence? +

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

Can I rate-limit remove_silence? +

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

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

remove_silence is provided by the Descript Complete MCP server (josephtandle/descript-complete). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.