Register and manage reusable assets (logos, videos). Registered assets can be referenced by name in create_clip instead of full paths.
AI agents use manage_assets 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 creates and manages asset registrations, which are reversible data modifications. While it could enable workflow efficiency, an AI agent could maliciously register misleading or inappropriate logos/videos to be used in clip generation, or exhaust storage by registering many large assets. The impact is bounded by the asset system itself (not system-wide), so severity is medium rather than high.
From the tool's definition Tool description states 'Register and manage reusable assets (logos, videos)' and 'Registered assets can be referenced by name' — these are create/modify operations that establish new named references in a system.
Documented attack patterns abuse exactly the kind of access manage_assets 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_assets:
{
"version": "1",
"default": "deny",
"tools": {
"manage_assets": {
"limits": [
{
"counter": "manage_assets_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}manage_assets 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.
Register and manage reusable assets (logos, videos). Registered assets can be referenced by name in create_clip instead of full paths. 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_assets: 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_assets 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_assets 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_assets. 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_assets 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.