Low Risk

list_tasks

List tasks with optional status filter.

How to control list_tasks ↓

What list_tasks does on N2n Nexus

AI agents call list_tasks to retrieve information from N2n Nexus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why list_tasks needs a policy

This tool retrieves or queries task data based on optional filters. The verb 'list' is a read operation that does not create, modify, delete, or execute any external operations. The optional status filter narrows the query but remains a passive retrieval. No destructive, financial, or code execution capabilities are implied. Confidence is high because the name and description clearly indicate read-only behavior.

From the tool's definition Tool name 'list_tasks' and description 'List tasks with optional status filter' indicate a query/retrieval operation with no data modification or side effects.

Documented attack patterns abuse exactly the kind of access list_tasks gives an agent:

How to control list_tasks

PolicyLayer is an MCP gateway — it sits between your AI agents and N2n Nexus, and nothing reaches the server without passing your rules. This is the rule we recommend for list_tasks:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_tasks": {}
  }
}

list_tasks is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register N2n Nexus — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about list_tasks

What does the list_tasks tool do? +

List tasks with optional status filter. It is categorised as a Read tool in the N2n Nexus MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_tasks? +

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

What risk level is list_tasks? +

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

Can I rate-limit list_tasks? +

Yes. Add a rate_limit block to the list_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 list_tasks completely? +

Set action: deny in the PolicyLayer policy for list_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 list_tasks? +

list_tasks is provided by the N2n Nexus MCP server (n2ns/n2n-nexus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every N2n Nexus tool call.

Start from N2n Nexus, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

22 N2n Nexus tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.