List all users in the Notion workspace.
AI agents call list_users to retrieve information from Notion MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves workspace user information without creating, modifying, deleting, executing code, or initiating financial transactions. The blast radius of misuse is minimal—an attacker gains visibility into workspace membership but cannot directly harm data or systems. While user enumeration can be a reconnaissance step in attacks, the tool itself performs no destructive action.
From the tool's definition Tool name is 'list_users' and description states 'List all users in the Notion workspace.' The verb 'list' and action of retrieving user information with no modification or deletion indicates a read-only query operation.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List all users in the Notion workspace. It is categorised as a Read tool in the Notion MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Notion MCP Server 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 Notion MCP Server. 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 Notion MCP Server MCP server (lrgex/notion-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 →