project_docs

What project_docs does on GNS3 MCP Server

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

Without an explicit description, the tool name strongly suggests this retrieves or queries documentation associated with projects—a Read operation with no side effects. The confidence is moderated due to the missing description. If this tool actually modifies, executes, or deletes project documentation, classification would change; however, 'docs' typically implies retrieval in lab/automation contexts.

From the tool's definition Tool name 'project_docs' suggests retrieval of documentation or metadata associated with GNS3 projects. The description is empty, which limits certainty, but the naming convention is consistent with read-only access patterns (e.g., 'export_topology_diagram'…

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

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

Questions about project_docs