query_resource

A read tool on the GNS3 MCP server.

SERVERGNS3 MCP Server SOURCEchistokhinsv/gns3-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/chistokhinsv-gns3-mcp/query-resource.md

WHAT IT DOES

What query_resource does on GNS3 MCP Server

AI agents call query_resource 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.

RISK

Why query_resource is rated Low

The name 'query_resource' aligns with Read operations (fetch/get semantics). Without a detailed description, confidence is moderate. The GNS3 context (network lab automation) suggests this likely retrieves node/project/topology information. No evidence of side effects, execution, or destructive capability. Assigned low severity due to read-only nature and limited blast radius if misused.

From the tool's definition Tool name 'query_resource' suggests data retrieval or inspection. Description is empty, limiting evidence. In GNS3 context, querying resources typically means retrieving status or configuration of network lab components without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

query_resource Allowed

query_resource is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY 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 query_resource call is checked against it from then on.

FAQ

Questions about query_resource

What does the query_resource tool do? +

query_resource is a read tool on the GNS3 MCP Server MCP server. It is categorised as a Read tool in the GNS3 MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_resource? +

Register the GNS3 MCP Server MCP server in PolicyLayer and add a rule for query_resource: 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 query_resource? +

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

Can I rate-limit query_resource? +

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

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

query_resource 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

claude_query on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →