New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

detect_silence

Analyzes a media file's audio for silent stretches using ffmpeg's silencedetect filter, run locally via child_process -- NOT via Premiere's scripting API, which has no audio-level/RMS reading capability at all (confirmed: every audio tool in this codebase only writes levels, never reads them). Re...

SERVERAdobe Premiere Pro SOURCEadobe-premiere-pro-mcp
Low RISK CLASS
Category Read
Parameters 40 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adobe-premiere-pro-mcp/detect-silence.md

What detect_silence does on Adobe Premiere Pro

AI agents call detect_silence to retrieve information from Adobe Premiere Pro without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
mediaPath string Direct filesystem path to the media file to analyze
projectItemId string Project item ID to resolve to a media path instead of passing mediaPath directly
noiseThresholdDb number Silence threshold in dBFS, e.g. -30 (default -30). Audio quieter than this is considered silent.
minDurationSeconds number Minimum duration in seconds for a quiet stretch to be reported as silence (default 1.5)

Parameters from the server's own tool schema.

Why detect_silence is rated Low

Even though detect_silence 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.

Risk signalsBulk/mass operation — affects multiple targets

Questions about detect_silence

What does the detect_silence tool do? +

Analyzes a media file's audio for silent stretches using ffmpeg's silencedetect filter, run locally via child_process -- NOT via Premiere's scripting API, which has no audio-level/RMS reading capability at all (confirmed: every audio tool in this codebase only writes levels, never reads them). Requires ffmpeg on PATH; returns an explicit error if it is not found rather than failing silently. This is DETECTION ONLY -- it does not cut or modify anything. Use the returned intervals with split_clip/ripple_delete/razor_timeline_at_time if you want to remove the silence. It is categorised as a Read tool in the Adobe Premiere Pro MCP Server, which means it retrieves data without modifying state.

What parameters does detect_silence accept? +

detect_silence accepts 4 parameters: mediaPath, projectItemId, noiseThresholdDb, minDurationSeconds. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on detect_silence? +

Register the Adobe Premiere Pro MCP server in PolicyLayer and add a rule for detect_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 Adobe Premiere Pro. Nothing to install.

What risk level is detect_silence? +

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

Can I rate-limit detect_silence? +

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

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

detect_silence is provided by the Adobe Premiere Pro MCP server (adobe-premiere-pro-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Adobe Premiere Pro, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Adobe Premiere Pro's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.