list_node_tasks

A read tool on the Proxmox MCP server.

SERVERProxmox MCP Server SOURCEgethosthewalrus/proxmox-mcp

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/gethosthewalrus-proxmox-mcp/list-node-tasks.md

WHAT IT DOES

What list_node_tasks does on Proxmox MCP Server

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

RISK

Why list_node_tasks is rated Low

The tool appears to retrieve or query task information from Proxmox nodes without performing side effects. Despite the empty description limiting certainty, the naming convention strongly suggests this is a passive information-gathering operation. In a Proxmox context, listing node tasks would be analogous to status queries that do not alter infrastructure state.

From the tool's definition Tool name 'list_node_tasks' indicates a listing/querying operation with no modification or execution suggested. The 'list' verb is a clear indicator of a Read operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_node_tasks safely

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

list_node_tasks Allowed

list_node_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": {
    "list_node_tasks": {}
  }
}

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

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

FAQ

Questions about list_node_tasks

What does the list_node_tasks tool do? +

list_node_tasks is a read tool on the Proxmox MCP Server MCP server. It is categorised as a Read tool in the Proxmox MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_node_tasks? +

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

What risk level is list_node_tasks? +

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

Can I rate-limit list_node_tasks? +

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

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

list_node_tasks is provided by the Proxmox MCP Server MCP server (gethosthewalrus/proxmox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Proxmox MCP Server, and thousands of servers like it.

This server

All 286 Proxmox MCP Server tools →

Across the catalogue

list_tasks on 0rca Dojo MCP Server →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

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