AI agents use create_asana_task to create or update resources in UnClick — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Task name |
notes | string | — | Task description |
due_on | string | — | Due date (YYYY-MM-DD) |
api_key | string | — | |
assignee | string | — | Assignee GID or 'me' |
projects | array | — | Project GIDs to add the task to |
workspace_gid | string | Yes | Workspace GID |
Parameters from the server's own tool schema.
This tool creates new records (tasks) in Asana, which is a reversible Write operation. It modifies project state by adding task data, but the action can be undone by deleting the task. It does not execute arbitrary code, delete data irreversibly, or move money. Severity is medium because task creation could spam a workspace or create misleading records, but the impact is contained to task data and reversible.
From the tool's definition Tool name is 'create_asana_task' and description states 'Create a new task in Asana.' The verb 'create' and action of adding a new task to a project management system indicates data creation.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
Create a new task in Asana. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_asana_task accepts 7 parameters: name, notes, due_on, api_key, assignee, projects, workspace_gid. Required: name, 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 create_asana_task: 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.
create_asana_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_asana_task 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 create_asana_task. 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.
create_asana_task 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 →