notification

What notification does on GNS3 MCP Server

AI agents call notification to retrieve information from GNS3 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 notification is rated Low

Without description details, classification is uncertain. The name 'notification' most likely indicates reading/retrieving notification data from GNS3, which would be a Read operation with low blast radius. However, confidence is reduced due to lack of concrete evidence in the description. If the tool actually modifies notification state or triggers actions, recategorization would be warranted.

From the tool's definition Tool name 'notification' with empty description provides minimal context. The name suggests retrieval or monitoring of notifications rather than state-changing operations.

The rule that runs notification safely

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "notification": {}
  }
}

Questions about notification