Low Risk

asana_list_workspaces

List all Asana workspaces accessible by the current user.

How to control asana_list_workspaces ↓

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

Low Risk

This tool retrieves and enumerates workspace metadata that the user already has access to. It performs a query operation with no capability to modify, delete, or execute actions. The scope is limited to listing accessible resources, making it a straightforward Read operation with minimal risk even if misused by an AI agent.

From the tool's definition Tool name 'asana_list_workspaces' combined with description 'List all Asana workspaces' indicates a retrieval operation with no modification or side effects.

Documented attack patterns abuse exactly the kind of access asana_list_workspaces gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and autoMate, and nothing reaches the server without passing your rules. This is the rule we recommend for asana_list_workspaces:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "asana_list_workspaces": {}
  }
}

asana_list_workspaces is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register autoMate — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the asana_list_workspaces tool do? +

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

How do I enforce a policy on asana_list_workspaces? +

Register the autoMate 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 autoMate. 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 autoMate MCP server (yuruotong1/automate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every autoMate tool call.

Deterministic rules across all 128 autoMate tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

128 autoMate tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.