media_transcode
Transcode one absolute local media path directly with ImageMagick or ffmpeg using Omarchy-equivalent format/resolution settings. No clipboard, notifications, shell, network, overwrite, or interactive menu.
This record as markdown: /tools/omarchy-mcp/media-transcode.md
What media_transcode does on Omarchy-MCP
AI agents invoke media_transcode to trigger actions in Omarchy-MCP. 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 media_transcode is rated High
Runs ffmpeg/ImageMagick on arbitrary local files, executing external processes with broad filesystem access.
From the tool's definition Transcode one absolute local media path directly with ImageMagick or ffmpeg
Attacks that exploit this kind of access
The rule that runs media_transcode safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Omarchy-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For media_transcode, this is the rule to start with:
media_transcode 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Omarchy-MCP, apply this rule, and every media_transcode call is checked against it from then on.
Questions about media_transcode
Transcode one absolute local media path directly with ImageMagick or ffmpeg using Omarchy-equivalent format/resolution settings. No clipboard, notifications, shell, network, overwrite, or interactive menu. It is categorised as a Execute tool in the Omarchy-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Omarchy MCP server in PolicyLayer and add a rule for media_transcode: 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 Omarchy-MCP. Nothing to install.
media_transcode is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the media_transcode 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_transcode. 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_transcode is provided by the Omarchy MCP server (hlsitechio/Omarchy-MCP). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Omarchy, and thousands of servers like it.
Across the catalogue