media_probe
Reports duration_ms, width, height, fps, whether it has audio, and file size for a video/audio file. Call it before editing to reason about the footage (compute trim ranges, pick a reframe crop). No permission required.
This record as markdown: /tools/com-local-mcp-local-mcp/media-probe.md
What media_probe does on Local
AI agents call media_probe to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Path to the media file. |
Parameters from the server's own tool schema.
Why media_probe is rated Low
media_probe retrieves and reports technical metadata about media files without modifying, executing, or deleting anything. It is purely a read operation that gathers information to inform subsequent decisions. The low severity reflects minimal risk even if misused—an AI agent could learn file characteristics but cannot alter data or trigger side effects.
From the tool's definition Tool 'Reports duration_ms, width, height, fps, whether it has audio, and file size' - purely retrieves metadata about media files with 'No permission required' and explicitly stated use case is 'Call it before editing to reason about the footage'…
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs media_probe safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For media_probe, this is the rule to start with:
media_probe is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every media_probe call is checked against it from then on.
Questions about media_probe
Reports duration_ms, width, height, fps, whether it has audio, and file size for a video/audio file. Call it before editing to reason about the footage (compute trim ranges, pick a reframe crop). No permission required. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
media_probe accepts 1 parameter: path. Required: path. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for media_probe: 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 Local. Nothing to install.
media_probe 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 media_probe 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 media_probe. 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.
media_probe is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue