asana_list_workspaces

List all Asana workspaces accessible to the authenticated user.

SERVERIntegrations MCP SOURCEshriram-vasudevan/integrations-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/shriram-vasudevan-integrations-mcp/asana-list-workspaces.md

WHAT IT DOES

What asana_list_workspaces does on Integrations MCP

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

RISK

Why asana_list_workspaces is rated Low

This is a read-only operation that queries and returns workspace information. It has no capability to modify, delete, or execute actions. The blast radius is minimal—an AI agent using this tool can only enumerate workspaces the user already has access to, which is low risk.

From the tool's definition Tool name and description clearly indicate a list operation: 'List all Asana workspaces accessible to the authenticated user.' This retrieves workspace metadata with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs asana_list_workspaces safely

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

asana_list_workspaces Allowed

asana_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": {
    "asana_list_workspaces": {}
  }
}

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

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

FAQ

Questions about asana_list_workspaces

What does the asana_list_workspaces tool do? +

List all Asana workspaces accessible to the authenticated user. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on asana_list_workspaces? +

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

What risk level is asana_list_workspaces? +

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

Can I rate-limit asana_list_workspaces? +

Yes. Add a rate_limit block to the asana_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 asana_list_workspaces completely? +

Set action: deny in the PolicyLayer policy for asana_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 asana_list_workspaces? +

asana_list_workspaces is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Integrations, and thousands of servers like it.

This server

All 420 Integrations 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 →