proxmox_lxc_notes_read

Read LXC description/notes with format detection and secret reference parsing

SERVERMCP Proxmox Server SOURCEbsahane/mcp-proxmox

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/bsahane-mcp-proxmox/proxmox-lxc-notes-read.md

WHAT IT DOES

What proxmox_lxc_notes_read does on MCP Proxmox Server

AI agents call proxmox_lxc_notes_read 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.

RISK

Why proxmox_lxc_notes_read is rated Low

This tool retrieves metadata (description/notes) from LXC containers without modifying state, executing code, or causing side effects. The format detection and secret reference parsing are informational operations only. While it may expose sensitive information in notes (lowering severity from critical), the action itself is read-only data retrieval.

From the tool's definition Tool name includes 'read' and description states 'Read LXC description/notes' with no modification, deletion, or execution capabilities mentioned.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs proxmox_lxc_notes_read 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_lxc_notes_read, this is the rule to start with:

proxmox_lxc_notes_read Allowed

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

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

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

FAQ

Questions about proxmox_lxc_notes_read

What does the proxmox_lxc_notes_read tool do? +

Read LXC description/notes with format detection and secret reference parsing. It is categorised as a Read tool in the MCP Proxmox Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on proxmox_lxc_notes_read? +

Register the MCP Proxmox Server MCP server in PolicyLayer and add a rule for proxmox_lxc_notes_read: 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.

What risk level is proxmox_lxc_notes_read? +

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

Can I rate-limit proxmox_lxc_notes_read? +

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

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

proxmox_lxc_notes_read 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.

KEEP EXPLORING

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

This server

All 124 MCP Proxmox Server tools →

Across the catalogue

claude_read_file on Claude Bridge → The MCP Attack Database →

Guides

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