获取支持的视频格式
AI agents call get_video_formats to retrieve information from Auto Video Generator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward query/list operation that retrieves metadata about supported video formats. It has no side effects, does not create, modify, or delete data, and does not execute code or trigger external operations. It falls clearly into the Read category with low severity since the worst outcome of misuse would be retrieving format information irrelevant to the task at hand.
From the tool's definition Tool name 'get_video_formats' and description '获取支持的视频格式' (get supported video formats) indicate a query operation that retrieves information about available video format options without modifying any data or triggering external operations.
Attacks that exploit this kind of access
获取支持的视频格式. It is categorised as a Read tool in the Auto Video Generator MCP Server, which means it retrieves data without modifying state.
Register the Auto Video Generator MCP server in PolicyLayer and add a rule for get_video_formats: 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 Auto Video Generator. Nothing to install.
get_video_formats 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_video_formats 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_video_formats. 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_video_formats is provided by the Auto Video Generator MCP server (zgmurder/auto_video_generator-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 →