my_tool

A other tool on the GNS3 MCP server.

SERVERGNS3 MCP Server SOURCEchistokhinsv/gns3-mcp

Low RISK CLASS

Category Other

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/chistokhinsv-gns3-mcp/my-tool.md

WHAT IT DOES

What my_tool does on GNS3 MCP Server

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

RISK

Why my_tool is rated Low

The description is completely empty and the generic name 'my_tool' provides no meaningful signal about what the tool does. While the server context (GNS3 network lab automation) suggests potential for Execute or Write operations, there is insufficient evidence to assign a specific category. Confidence is very low. Defaulting to Other with low severity until more information is available.

From the tool's definition Tool name is 'my_tool' with an empty description, providing no information about its functionality.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

my_tool Rate-limited

my_tool gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "my_tool": {
      "limits": [
        {
          "counter": "my_tool_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect GNS3 MCP Server, apply this rule, and every my_tool call is checked against it from then on.

FAQ

Questions about my_tool

What does the my_tool tool do? +

my_tool is a other tool on the GNS3 MCP Server MCP server. It is categorised as a Other tool in the GNS3 MCP Server MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on my_tool? +

Register the GNS3 MCP Server MCP server in PolicyLayer and add a rule for my_tool: 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 GNS3 MCP Server. Nothing to install.

What risk level is my_tool? +

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

Can I rate-limit my_tool? +

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

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

my_tool is provided by the GNS3 MCP Server MCP server (chistokhinsv/gns3-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GNS3 MCP Server, and thousands of servers like it.

This server

All 16 GNS3 MCP Server tools →

Across the catalogue

async_tool on Enhanced Image Analysis MCP Server →async_tool on Agent Jail →my_tool on Agentic Automl Platform → The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →