Create a render for a selected Project template or Design variant with specified parameters. How to use: - Call this after the user selects a candidate from \
AI agents invoke render_item to trigger actions in Plainly Videos MCP Server. 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.
This tool initiates an external video rendering job, which is an irreversible external operation that consumes API resources and compute. It is not purely a write (data creation/modification) but an execution of a media processing pipeline. Misuse could result in unintended renders being submitted at scale, consuming credits or quota, making it high severity.
From the tool's definition "Create a render for a selected Project template or Design variant with specified parameters" — triggers an external rendering operation via Plainly's API
Documented attack patterns abuse exactly the kind of access render_item gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Plainly Videos MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for render_item:
{
"version": "1",
"default": "deny",
"tools": {
"render_item": {
"limits": [
{
"counter": "render_item_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}render_item 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.
Free to start. No card required.
Create a render for a selected Project template or Design variant with specified parameters. How to use: - Call this after the user selects a candidate from \. It is categorised as a Execute tool in the Plainly Videos MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Plainly Videos MCP Server MCP server in PolicyLayer and add a rule for render_item: 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 Plainly Videos MCP Server. Nothing to install.
render_item 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 render_item 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 render_item. 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.
render_item is provided by the Plainly Videos MCP Server MCP server (plainly-videos/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Plainly Videos MCP Server, 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.
4 Plainly Videos MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.