Check the status of a render job. Available states: - PENDING: The render job has been created but not yet added to the queue. - THROTTLED: The render job is waiting due to rate limiting. It will be started as soon as a slot opens, no need for manual retries. - QUEUED: The render job is in the qu...
AI agents call check_render_status to retrieve information from Plainly Videos MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure read operation that queries the status of an existing render job without side effects. It retrieves state information to inform the caller but does not trigger, modify, or cancel any jobs. The tool fits the Read category: retrieves or queries data with no side effects.
From the tool's definition Tool name is 'check_render_status' and description states it 'Check[s] the status of a render job' by returning state information (PENDING, QUEUED, IN_PROGRESS, DONE, FAILED, INVALID).
Documented attack patterns abuse exactly the kind of access check_render_status 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 check_render_status:
{
"version": "1",
"default": "deny",
"tools": {
"check_render_status": {}
}
}check_render_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check the status of a render job. Available states: - PENDING: The render job has been created but not yet added to the queue. - THROTTLED: The render job is waiting due to rate limiting. It will be started as soon as a slot opens, no need for manual retries. - QUEUED: The render job is in the queue and will start soon. - IN_PROGRESS: The render job is currently being processed. - DONE: The render job has completed successfully. The output URL will be provided. - FAILED: The render job encountered an error and did not complete successfully. Error details will be provided. - INVALID: The render job was invalid (e.g., due to incorrect parameters). Error details will be provided. - CANCELLED: The render job was cancelled by the user. Response format: - Always include a link to the render details page. - If the render is still in progress (PENDING, THROTTLED, QUEUED, IN_PROGRESS) tell user to check the status again later. - If the render is DONE, return the output URL and the render page details. - If the render FAILED or is INVALID, return the error message and details. Use when: - You need to check the progress of a render job - You want to retrieve the final render output URL - You want to retrieve render error details if the job failed. It is categorised as a Read tool in the Plainly Videos MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Plainly Videos MCP Server MCP server in PolicyLayer and add a rule for check_render_status: 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.
check_render_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_render_status 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 check_render_status. 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.
check_render_status 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.