update_asana_task · UnClick MCP: Risk & Policy

WHAT IT DOES

What update_asana_task does on UnClick

AI agents use update_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.

PARAMETERS

Parameter	Type	Required	Description
`name`	string	—
`notes`	string	—
`due_on`	string	—	YYYY-MM-DD or null to clear
`api_key`	string	—
`assignee`	string	—	Assignee GID or null to unassign
`task_gid`	string	Yes	Task GID
`completed`	boolean	—

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why update_asana_task needs a policy

This tool modifies existing project management data in Asana. It is reversible (the task can be updated again with different values), so it falls under Write rather than Destructive.

From the tool's definition Tool name is 'update_asana_task' and description states it will 'Update an existing Asana task.' The verb 'update' indicates modification of existing data.

Risk signalsHandles credentials or secrets (api_key)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_asana_task Rate-limited

update_asana_task stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_asana_task": {
      "limits": [
        {
          "counter": "update_asana_task_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches UnClick, so you can run agents against it safely.

FAQ

Questions about update_asana_task

What does the update_asana_task tool do? +

Update an existing Asana task. 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.

What parameters does update_asana_task accept? +

update_asana_task accepts 7 parameters: name, notes, due_on, api_key, assignee, task_gid, completed. Required: task_gid. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_asana_task? +

Register the UnClick MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_asana_task? +

update_asana_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_asana_task? +

Yes. Add a rate_limit block to the update_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.

How do I block update_asana_task completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_asana_task? +

update_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.