Check if all required dependencies (yt-dlp, whisper, ffmpeg) are installed
AI agents call check_dependencies to retrieve information from Video Transcriber MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a diagnostic check of system state (whether software packages exist) and returns information. It retrieves status information without modifying, executing, or affecting any data or external systems. This is a pure Read operation with minimal blast radius even if misused by an AI agent.
From the tool's definition Tool name is 'check_dependencies' and description states it checks if required dependencies 'are installed' — a query operation with no side effects.
Attacks that exploit this kind of access
Check if all required dependencies (yt-dlp, whisper, ffmpeg) are installed. It is categorised as a Read tool in the Video Transcriber MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Video Transcriber MCP Server MCP server in PolicyLayer and add a rule for check_dependencies: 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 Video Transcriber MCP Server. Nothing to install.
check_dependencies is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_dependencies 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.
Set action: deny in the PolicyLayer policy for check_dependencies. 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.
check_dependencies is provided by the Video Transcriber MCP Server MCP server (nhatvu148/video-transcriber-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →