list_notification_endpoints
List all configured notification endpoints (sendmail, gotify, smtp, webhook).
This record as markdown: /tools/gethosthewalrus-proxmox-mcp/list-notification-endpoints.md
What list_notification_endpoints does on Proxmox MCP Server
AI agents call list_notification_endpoints 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.
Why list_notification_endpoints is rated Low
This tool retrieves and displays existing notification endpoint configurations without creating, modifying, deleting, or executing any operations. It is purely informational and has no capability to alter system state or trigger actions. The blast radius of misuse is minimal—an attacker could discover notification endpoints but cannot manipulate them or cause harm through listing alone.
From the tool's definition Tool name 'list_notification_endpoints' and description 'List all configured notification endpoints' indicate a query/retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_notification_endpoints 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_notification_endpoints, this is the rule to start with:
list_notification_endpoints 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 Proxmox MCP Server, apply this rule, and every list_notification_endpoints call is checked against it from then on.
Questions about list_notification_endpoints
List all configured notification endpoints (sendmail, gotify, smtp, webhook). It is categorised as a Read tool in the Proxmox MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for list_notification_endpoints: 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.
list_notification_endpoints 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 list_notification_endpoints 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 list_notification_endpoints. 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.
list_notification_endpoints 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.
More on Proxmox MCP Server, and thousands of servers like it.
This server
Across the catalogue