List projects in an Asana workspace.
AI agents call asana_list_projects to retrieve information from Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves project information from Asana without creating, modifying, deleting, or executing any operations. It has no side effects and presents minimal risk of misuse—at worst, an AI agent could enumerate projects, which is a low-impact information disclosure that would typically already be visible to authenticated users.
From the tool's definition Tool name 'asana_list_projects' and description 'List projects in an Asana workspace' indicate data retrieval with no modification. The verb 'list' is a read-only operation that queries and returns existing project data.
Attacks that exploit this kind of access
List projects in an Asana workspace. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Integrations MCP server in PolicyLayer and add a rule for asana_list_projects: 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.
asana_list_projects 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 asana_list_projects 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 asana_list_projects. 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.
asana_list_projects 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.
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 →