get_tasks

Get Asana tasks

SERVERNcp SOURCE@portel/ncp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-portel-dev-ncp/get-tasks.md

WHAT IT DOES

What get_tasks does on Ncp

AI agents call get_tasks to retrieve information from Ncp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_tasks is rated Low

This tool retrieves or queries task data from Asana without creating, modifying, deleting, or executing any operations. It is a pure read operation with minimal security impact, though severity depends on the sensitivity of task data exposed.

From the tool's definition Tool name is 'get_tasks' and description states 'Get Asana tasks' — this is a retrieval operation with no modification or execution capabilities.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_tasks safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_tasks, this is the rule to start with:

get_tasks Allowed

get_tasks is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_tasks": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ncp, apply this rule, and every get_tasks call is checked against it from then on.

FAQ

Questions about get_tasks

What does the get_tasks tool do? +

Get Asana tasks. It is categorised as a Read tool in the Ncp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_tasks? +

Register the Ncp MCP server in PolicyLayer and add a rule for get_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 Ncp. Nothing to install.

What risk level is get_tasks? +

get_tasks is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_tasks? +

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

How do I block get_tasks completely? +

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

What MCP server provides get_tasks? +

get_tasks is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ncp, and thousands of servers like it.

This server

All 275 Ncp tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →