list_workspaces

List the workspaces the authenticated user is actually a member of, with their role in each. Use before switch_workspace when a user belongs to more than one workspace.

SERVERAdrata SOURCE@adrata/adrata-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-adrata-mcp/list-workspaces.md

WHAT IT DOES

What list_workspaces does on Adrata

AI agents call list_workspaces to retrieve information from Adrata without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_workspaces is rated Low

Even though list_workspaces only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_workspaces safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Adrata, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_workspaces, this is the rule to start with:

list_workspaces Allowed

list_workspaces is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_workspaces": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Adrata, apply this rule, and every list_workspaces call is checked against it from then on.

FAQ

Questions about list_workspaces

What does the list_workspaces tool do? +

List the workspaces the authenticated user is actually a member of, with their role in each. Use before switch_workspace when a user belongs to more than one workspace. It is categorised as a Read tool in the Adrata MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_workspaces? +

Register the Adrata MCP server in PolicyLayer and add a rule for list_workspaces: 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 Adrata. Nothing to install.

What risk level is list_workspaces? +

list_workspaces is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_workspaces? +

Yes. Add a rate_limit block to the list_workspaces 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.

How do I block list_workspaces completely? +

Set action: deny in the PolicyLayer policy for list_workspaces. 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.

What MCP server provides list_workspaces? +

list_workspaces is provided by the Adrata MCP server (@adrata/adrata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Adrata, and thousands of servers like it.

This server

All 278 Adrata tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →