kaltura.user.update · Kaltura MCP Server MCP: Risk & Policy

WHAT IT DOES

What kaltura.user.update does on Kaltura MCP Server

AI agents use kaltura.user.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.

WHY IT NEEDS A POLICY

Why kaltura.user.update needs a policy

This tool modifies user records in Kaltura, which is a reversible operation (as opposed to deletion). While user data is sensitive, the update operation itself does not involve deletion, financial transactions, or code execution. The severity is medium because incorrect user updates could affect access controls or user metadata, but the operation is not destructive or financial in nature.

From the tool's definition Tool name 'kaltura.user.update' and description 'Update a user in Kaltura' indicate modification of user data. The verb 'update' is a classic write operation that creates or modifies data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

kaltura.user.update Rate-limited

kaltura.user.update stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "kaltura.user.update": {
      "limits": [
        {
          "counter": "kaltura.user.update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Kaltura MCP Server, so you can run agents against it safely.

FAQ

Questions about kaltura.user.update

What does the kaltura.user.update tool do? +

Update a user 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.

How do I enforce a policy on kaltura.user.update? +

Register the Kaltura MCP Server MCP server in PolicyLayer and add a rule for kaltura.user.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.

What risk level is kaltura.user.update? +

kaltura.user.update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit kaltura.user.update? +

Yes. Add a rate_limit block to the kaltura.user.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.

How do I block kaltura.user.update completely? +

Set action: deny in the PolicyLayer policy for kaltura.user.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.

What MCP server provides kaltura.user.update? +

kaltura.user.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.