List users in the organization. Defaults to active users; use the status filter to include pending, deactivated, or imported. Supports filtering by role, department, office, granted permissions, and a full-text query across name and email.
AI agents call list_users to retrieve information from Kula Ai without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries user data with no side effects. It performs read-only operations (list, filter, search) on user records. The ability to filter and search does not elevate this beyond a data retrieval operation. No data is created, modified, deleted, or executed.
From the tool's definition Tool description explicitly states it 'List users in the organization' with filtering capabilities for status, role, department, office, permissions, and full-text search across name and email.
Attacks that exploit this kind of access
List users in the organization. Defaults to active users; use the status filter to include pending, deactivated, or imported. Supports filtering by role, department, office, granted permissions, and a full-text query across name and email. It is categorised as a Read tool in the Kula Ai MCP Server, which means it retrieves data without modifying state.
Register the Kula Ai MCP server in PolicyLayer and add a rule for list_users: 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 Kula Ai. Nothing to install.
list_users 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 list_users 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 list_users. 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.
list_users is provided by the Kula Ai MCP server (kula-ai/kula-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
list_users is one line of Kula Ai's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →