Low Risk

via_task_list

List tasks from the Via shared task board.

How to control via_task_list ↓

What via_task_list does on Via

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

Low Risk

Why via_task_list needs a policy

This tool retrieves and displays existing tasks from a shared task board. It performs a read-only operation that queries data without creating, modifying, deleting, or executing any external actions. The blast radius of misuse is minimal—an agent could only access task information already visible to authorized users of the Via system.

From the tool's definition Tool name 'via_task_list' and description 'List tasks from the Via shared task board' indicates a query/retrieval operation with no modification or side effects.

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

How to control via_task_list

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

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

via_task_list 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 Via — 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 via_task_list

What does the via_task_list tool do? +

List tasks from the Via shared task board. It is categorised as a Read tool in the Via MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on via_task_list? +

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

What risk level is via_task_list? +

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

Can I rate-limit via_task_list? +

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

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

via_task_list is provided by the Via MCP server (vektor-memory/via). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Via tool call.

Start from Via, 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.

8 Via 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.