List all managed users in the workspace
AI agents call list_workspace_users to retrieve information from Publora 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 and enumerates user information from a workspace. It falls under the Read category as it performs a data retrieval operation with no side effects. Severity is medium rather than low because listing all users in a workspace could expose sensitive information about workspace membership and user identities, which could be exploited for social engineering, unauthorized access attempts, or privacy…
From the tool's definition Tool name 'list_workspace_users' and description 'List all managed users in the workspace' indicate a retrieval operation that queries user data without modification.
Attacks that exploit this kind of access
List all managed users in the workspace. It is categorised as a Read tool in the Publora MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Publora MCP Server MCP server in PolicyLayer and add a rule for list_workspace_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 Publora MCP Server. Nothing to install.
list_workspace_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_workspace_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_workspace_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_workspace_users is provided by the Publora MCP Server MCP server (publora/mcp-server). 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 →