Save, load, list, or delete rendering presets. Presets store caption_style, crop_strategy, logo_path, and outro_path for quick reuse.
AI agents use manage_presets 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 primarily performs reversible configuration management (save/load presets). The delete operation applies to preset templates, not final rendered clips or irreplaceable assets. Deletion of presets is recoverable through re-creation. This is categorized as Write rather than Destructive because the presets themselves are ephemeral configurations meant for reuse, not critical unique data.
From the tool's definition Tool description states it can 'Save, load, list, or delete rendering presets' — the save and delete operations modify stored configuration data.
Documented attack patterns abuse exactly the kind of access manage_presets 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 manage_presets:
{
"version": "1",
"default": "deny",
"tools": {
"manage_presets": {
"limits": [
{
"counter": "manage_presets_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}manage_presets 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.
Save, load, list, or delete rendering presets. Presets store caption_style, crop_strategy, logo_path, and outro_path for quick reuse. 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 manage_presets: 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.
manage_presets 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 manage_presets 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 manage_presets. 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.
manage_presets 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.