Update a media entry in Kaltura
AI agents use kaltura.media.update to create or update resources in Kaltura MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kaltura MCP Server environment.
The tool modifies media metadata or properties reversibly within Kaltura. While it changes data, updates are typically reversible through subsequent updates or version history, distinguishing it from destructive deletion operations.
From the tool's definition Tool name 'kaltura.media.update' and description 'Update a media entry in Kaltura' indicate modification of existing data without deletion.
Attacks that exploit this kind of access
Update a media entry in Kaltura. It is categorised as a Write tool in the Kaltura MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kaltura MCP Server MCP server in PolicyLayer and add a rule for kaltura.media.update: 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 Kaltura MCP Server. Nothing to install.
kaltura.media.update 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 kaltura.media.update 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 kaltura.media.update. 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.
kaltura.media.update is provided by the Kaltura MCP Server MCP server (zoharbabin/kaltura-mcp-legacy). 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 →