Lists all members of a specific workspace
AI agents call list_workspace_members to retrieve information from Keyshade without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves workspace membership information without creating, modifying, deleting, or executing any operations. It is a non-destructive read operation with minimal blast radius even if misused by an AI agent, as it only exposes existing membership data.
From the tool's definition Tool name 'list_workspace_members' and description 'Lists all members of a specific workspace' indicate a retrieval operation with no modification of data.
Documented attack patterns abuse exactly the kind of access list_workspace_members gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Keyshade, and nothing reaches the server without passing your rules. This is the rule we recommend for list_workspace_members:
{
"version": "1",
"default": "deny",
"tools": {
"list_workspace_members": {}
}
}list_workspace_members is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Lists all members of a specific workspace. It is categorised as a Read tool in the Keyshade MCP Server, which means it retrieves data without modifying state.
Register the Keyshade MCP server in PolicyLayer and add a rule for list_workspace_members: 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 Keyshade. Nothing to install.
list_workspace_members 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_members 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_members. 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_members is provided by the Keyshade MCP server (keyshade-xyz/keyshade-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Keyshade, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
44 Keyshade tools catalogued and risk-classified — across an index of 43,000+ MCP servers.