查询渲染状态。渲染中返回进度百分比和步骤描述；完成后返回视频下载链接。建议每 15 秒轮询一次。
AI agents call get_render_status to retrieve information from Flash Cast without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves status information about an ongoing render process—it fetches data with no side effects. It neither creates, modifies, deletes, executes arbitrary code, nor moves money. The polling pattern and download link provision are typical of monitoring and data retrieval operations. Classified as Read.
From the tool's definition The tool 查询渲染状态 (query render status) retrieves the progress percentage, step description, and video download link. The description uses 查询 (query) and recommends polling every 15 seconds, indicating a read-only status check operation.
Attacks that exploit this kind of access
查询渲染状态。渲染中返回进度百分比和步骤描述；完成后返回视频下载链接。建议每 15 秒轮询一次。. It is categorised as a Read tool in the Flash Cast MCP Server, which means it retrieves data without modifying state.
Register the Flash Cast MCP server in PolicyLayer and add a rule for get_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 Flash Cast. Nothing to install.
get_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 get_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 get_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.
get_render_status is provided by the Flash Cast MCP server (trtian/flash-cast-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →