Set the working video file without transcribing. Use this when you
AI agents use set_video to create or update resources in Podcli — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Podcli environment.
This tool modifies the application's working state by setting which video file is currently active for processing. While it doesn't create permanent data structures or irreversibly delete content, it does change the internal state that other tools will operate on (e.g., create_clip will process this selected video). This is a Write operation rather than Read because it has side effects on the application state.
From the tool's definition Tool name 'set_video' and description 'Set the working video file' indicate modification of application state by selecting/changing a video file for processing.
Documented attack patterns abuse exactly the kind of access set_video gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Podcli, and nothing reaches the server without passing your rules. This is the rule we recommend for set_video:
{
"version": "1",
"default": "deny",
"tools": {
"set_video": {
"limits": [
{
"counter": "set_video_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} set_video stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Set the working video file without transcribing. Use this when you. It is categorised as a Write tool in the Podcli MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Podcli MCP server in PolicyLayer and add a rule for set_video: 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 Podcli. Nothing to install.
set_video is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_video 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 set_video. 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.
set_video is provided by the Podcli MCP server (nmbrthirteen/podcli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Podcli, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 Podcli tools catalogued and risk-classified — across an index of 43,000+ MCP servers.