proxmox_task_status
A read tool on the MCP Proxmox MCP server.
This record as markdown: /tools/bsahane-mcp-proxmox/proxmox-task-status.md
What proxmox_task_status does on MCP Proxmox Server
AI agents call proxmox_task_status to retrieve information from MCP Proxmox Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why proxmox_task_status is rated Low
Task status monitoring is fundamentally a read operation that retrieves information about ongoing or completed operations without side effects. While the empty description reduces confidence slightly, the tool name and position among other Proxmox management tools (which include write/execute operations like backup_vm, clone_vm, and ansible_playbook) strongly suggest this is a query/status-retrieval function.
From the tool's definition Tool name 'proxmox_task_status' indicates retrieval of task status information. No description provided, but the naming convention and context within a Proxmox management MCP server suggest this queries operational state rather than modifying or executing…
Attacks that exploit this kind of access
The rule that runs proxmox_task_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Proxmox Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For proxmox_task_status, this is the rule to start with:
proxmox_task_status 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 MCP Proxmox Server, apply this rule, and every proxmox_task_status call is checked against it from then on.
Questions about proxmox_task_status
proxmox_task_status is a read tool on the MCP Proxmox Server MCP server. It is categorised as a Read tool in the MCP Proxmox Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Proxmox Server MCP server in PolicyLayer and add a rule for proxmox_task_status: 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 MCP Proxmox Server. Nothing to install.
proxmox_task_status 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 proxmox_task_status 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 proxmox_task_status. 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.
proxmox_task_status is provided by the MCP Proxmox Server MCP server (bsahane/mcp-proxmox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Proxmox Server, and thousands of servers like it.
This server
Across the catalogue