This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/get-asana-task.md
What get_asana_task does on UnClick
AI agents call get_asana_task 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 |
|---|---|---|---|
api_key | string | — | |
task_gid | string | Yes | Task GID |
Parameters from the server's own tool schema.
Why get_asana_task is rated Low
This tool retrieves information about an Asana task without creating, modifying, deleting, or executing anything. It is a straightforward read operation that queries existing data. Severity is low because exposing task details has minimal blast radius unless the tasks contain highly sensitive business information, but the default assumption for a read operation is low risk.
From the tool's definition Tool name 'get_asana_task' and description 'Get full details of a single Asana task' clearly indicate a data retrieval operation with no modification or side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs get_asana_task 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 get_asana_task, this is the rule to start with:
get_asana_task 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 get_asana_task call is checked against it from then on.
Questions about get_asana_task
Get full details of a single Asana task. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
get_asana_task accepts 2 parameters: api_key, task_gid. Required: task_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 get_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.
get_asana_task 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 get_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 get_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.
get_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.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue