update_video
AI agents use update_video to create or update resources in Reka Vision MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Reka Vision MCP Server environment.
The 'update_' prefix conventionally indicates a Write operation that modifies existing data. Without an explicit description, we infer from context: the server manages video data, and update_video likely modifies video properties, metadata, or associated information (tags, groups, etc.) without deleting it. This is reversible (opposite of Destructive) and does not execute external code (unlike Execute).
From the tool's definition Tool name is 'update_video' which indicates modification of video data. The description is empty, but based on the sibling tools on this server (upload, index, delete, get operations on videos), this tool modifies existing video records or metadata reversibly.
Attacks that exploit this kind of access
update_video. It is categorised as a Write tool in the Reka Vision MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Reka Vision MCP Server MCP server in PolicyLayer and add a rule for update_video: 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 Reka Vision MCP Server. Nothing to install.
update_video is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_video 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 update_video. 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.
update_video is provided by the Reka Vision MCP Server MCP server (reka-ai/reka-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 →