Adjust a suggested clip before exporting. Change timing, title, or caption style.
AI agents use modify_clip 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.
The tool performs reversible modifications to clip metadata and properties (timing adjustments, title changes, caption style updates) without deleting data or executing arbitrary code. This is characteristic of Write operations. Severity is medium because misuse could result in incorrect or inappropriate clip exports, but the changes are reversible and localized to a single clip's properties.
From the tool's definition Tool description states 'Adjust a suggested clip before exporting. Change timing, title, or caption style.' This involves modifying existing clip data (timing, title, caption properties) prior to export, which constitutes data modification rather than…
Documented attack patterns abuse exactly the kind of access modify_clip 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 modify_clip:
{
"version": "1",
"default": "deny",
"tools": {
"modify_clip": {
"limits": [
{
"counter": "modify_clip_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} modify_clip 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.
Adjust a suggested clip before exporting. Change timing, title, or caption style. 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 modify_clip: 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.
modify_clip 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 modify_clip 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 modify_clip. 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.
modify_clip 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.