List users from Kaltura
AI agents call kaltura.user.list to retrieve information from Kaltura MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query to list users. It has no capability to modify, delete, or create user records, nor does it execute arbitrary code or trigger external operations. The blast radius of misuse is minimal—an AI agent listing users could expose user information but cannot alter system state. This is classified as a Read operation with low severity.
From the tool's definition Tool name 'kaltura.user.list' and description 'List users from Kaltura' indicate a retrieval operation with no side effects. The 'list' operation is a standard query function that retrieves and displays existing user data without modification or deletion.
Attacks that exploit this kind of access
List users from Kaltura. It is categorised as a Read tool in the Kaltura MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kaltura MCP Server MCP server in PolicyLayer and add a rule for kaltura.user.list: 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.user.list 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 kaltura.user.list 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.user.list. 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.user.list 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 →