视频截帧(支持持久化)
AI agents invoke tos_video_snapshot to trigger actions in TOS 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 executes a video frame extraction operation, which is an active media processing task. The '持久化' (persistence) aspect means it can also write output to storage. Since it triggers an external processing operation (Execute) and may write data (Write), Execute is the more severe applicable category. It does not delete or move money, so Financial/Destructive don't apply.
From the tool's definition 视频截帧(支持持久化) — 'video snapshot with persistence support' triggers a media processing operation (frame extraction from video) and optionally persists/writes the result to storage
Attacks that exploit this kind of access
视频截帧(支持持久化). It is categorised as a Execute tool in the TOS MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TOS MCP Server MCP server in PolicyLayer and add a rule for tos_video_snapshot: 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 TOS MCP Server. Nothing to install.
tos_video_snapshot 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 tos_video_snapshot 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 tos_video_snapshot. 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.
tos_video_snapshot is provided by the TOS MCP Server MCP server (jneless/tos-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 →