# node_file

A other tool on the GNS3 MCP Server MCP server.

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

## Facts

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

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

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

## Why node_file is rated Low

The description is empty, so the exact behavior cannot be determined. The name 'node_file' on a GNS3 server suggests file read/write operations on network node configurations, which could range from Read to Destructive depending on implementation. Given the ambiguity, defaulting to Other with low confidence. The severity is medium because file operations on network nodes could impact lab configurations if misused.

From the tool's own definition: "Tool name is 'node_file' but description is empty/uninformative. Name suggests file operations on GNS3 nodes."

## Use case

AI agents call node_file as a supporting operation in GNS3 MCP Server workflows.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "node_file": {
      "limits": [
        {
          "counter": "node_file_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## 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
- `project` — Other — https://policylayer.com/tools/chistokhinsv-gns3-mcp/project.md
- `tftp` — Other — https://policylayer.com/tools/chistokhinsv-gns3-mcp/tftp.md
- `notification` — Read — https://policylayer.com/tools/chistokhinsv-gns3-mcp/notification.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