list_notification_targets

List all notification targets.

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-notification-targets.md

WHAT IT DOES

What list_notification_targets does on Proxmox MCP Server

AI agents call list_notification_targets 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_notification_targets is rated Low

This tool retrieves configuration data about notification targets without creating, modifying, or deleting anything. It has no side effects and poses minimal risk if misused by an AI agent—the worst outcome would be information disclosure of notification endpoint metadata.

From the tool's definition Tool name 'list_notification_targets' and description 'List all notification targets' indicate a query/retrieval operation with no side effects. The verb 'list' is explicitly identified in the classification rules as a Read category action.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_notification_targets Allowed

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

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_notification_targets call is checked against it from then on.

FAQ

Questions about list_notification_targets

What does the list_notification_targets tool do? +

List all notification targets. 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_notification_targets? +

Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for list_notification_targets: 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_notification_targets? +

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

Can I rate-limit list_notification_targets? +

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

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

list_notification_targets 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

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

Guides

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