# notification

A read tool on the GNS3 MCP Server MCP server.

Agent View of the PolicyLayer registry record for `notification`. HTML page: https://policylayer.com/tools/chistokhinsv-gns3-mcp/notification

## Facts

- Tool: `notification`
- Server: GNS3 MCP Server (`chistokhinsv/gns3-mcp`) — https://policylayer.com/tools/chistokhinsv-gns3-mcp.md
- Homepage: https://github.com/ChistokhinSV/gns3-mcp
- Risk category: Read (Low risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "notification",
    "arguments": {}
  }
}
```

## 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 own definition: "Tool name 'notification' with empty description provides minimal context. The name suggests retrieval or monitoring of notifications rather than state-changing operations."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches GNS3 MCP Server:

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

## Other tools on GNS3 MCP Server (15)

- `console` — Execute — https://policylayer.com/tools/chistokhinsv-gns3-mcp/console.md
- `http_client` — Execute — https://policylayer.com/tools/chistokhinsv-gns3-mcp/http-client.md
- `node` — Execute — https://policylayer.com/tools/chistokhinsv-gns3-mcp/node.md
- `ssh` — Execute — https://policylayer.com/tools/chistokhinsv-gns3-mcp/ssh.md
- `drawing` — Other — https://policylayer.com/tools/chistokhinsv-gns3-mcp/drawing.md
- `gns3_connection` — Other — https://policylayer.com/tools/chistokhinsv-gns3-mcp/gns3-connection.md
- `link` — Other — https://policylayer.com/tools/chistokhinsv-gns3-mcp/link.md
- `my_tool` — Other — https://policylayer.com/tools/chistokhinsv-gns3-mcp/my-tool.md
- `node_file` — Other — https://policylayer.com/tools/chistokhinsv-gns3-mcp/node-file.md
- `project` — Other — https://policylayer.com/tools/chistokhinsv-gns3-mcp/project.md
- `tftp` — Other — https://policylayer.com/tools/chistokhinsv-gns3-mcp/tftp.md
- `project_docs` — Read — https://policylayer.com/tools/chistokhinsv-gns3-mcp/project-docs.md
- `query_resource` — Read — https://policylayer.com/tools/chistokhinsv-gns3-mcp/query-resource.md
- `search_tools` — Read — https://policylayer.com/tools/chistokhinsv-gns3-mcp/search-tools.md
- `export_topology_diagram` — Write — https://policylayer.com/tools/chistokhinsv-gns3-mcp/export-topology-diagram.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=chistokhinsv-gns3-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/chistokhinsv-gns3-mcp