This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/list-asana-projects.md
What list_asana_projects does on UnClick
AI agents call list_asana_projects to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Max results (default 100) |
api_key | string | — | |
archived | boolean | — | Include archived projects (default false) |
workspace_gid | string | Yes | Workspace GID |
Parameters from the server's own tool schema.
Why list_asana_projects is rated Low
This tool queries and returns a list of existing projects from Asana without creating, modifying, deleting, or executing any operations. It is a passive data retrieval action typical of Read category tools. Severity is low because accessing project metadata poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'list_asana_projects' and description 'List projects in an Asana workspace' indicate a retrieval operation with no side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs list_asana_projects safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_asana_projects, this is the rule to start with:
list_asana_projects is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every list_asana_projects call is checked against it from then on.
Questions about list_asana_projects
List projects in an Asana workspace. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
list_asana_projects accepts 4 parameters: limit, api_key, archived, workspace_gid. Required: workspace_gid. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for list_asana_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 UnClick. Nothing to install.
list_asana_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 list_asana_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 list_asana_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.
list_asana_projects is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue