AI agents call search_asana_tasks to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | Yes | Search query |
limit | number | — | |
api_key | string | — | |
completed | boolean | — | |
workspace_gid | string | Yes | Workspace GID |
Parameters from the server's own tool schema.
This tool performs a search query on existing Asana tasks, which is a non-destructive read operation. The word 'search' and the absence of any language indicating creation, modification, or deletion of data confirms this is a Read category tool. Severity is low because search operations have minimal blast radius—misuse would only expose information already accessible to the authenticated user.
From the tool's definition Tool name 'search_asana_tasks' and description 'Search tasks by text within an Asana workspace' indicate a read-only query operation that retrieves task data without modifying, executing, or deleting anything.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
Search tasks by text within an Asana workspace. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
search_asana_tasks accepts 5 parameters: text, limit, api_key, completed, workspace_gid. Required: text, 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 search_asana_tasks: 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.
search_asana_tasks 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 search_asana_tasks 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 search_asana_tasks. 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.
search_asana_tasks 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.
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 →