Low Risk

network_query

Query network devices using natural language

How to control network_query ↓

AI agents call network_query to retrieve information from OPNSense MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

The tool performs network queries to retrieve device information. No modification, deletion, code execution, or financial operations are implied. Querying network state has minimal blast radius unless it exposes sensitive information about the firewall topology, but the core action is inspection only. Classified as Read with low severity.

From the tool's definition Tool name 'network_query' and description 'Query network devices using natural language' indicate data retrieval without modification. The verb 'query' combined with 'network devices' suggests read-only operations that retrieve information.

Documented attack patterns abuse exactly the kind of access network_query gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and OPNSense MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for network_query:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "network_query": {}
  }
}

network_query is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register OPNSense MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the network_query tool do? +

Query network devices using natural language. It is categorised as a Read tool in the OPNSense MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on network_query? +

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

What risk level is network_query? +

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

Can I rate-limit network_query? +

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

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

network_query is provided by the OPNSense MCP Server MCP server (vespo92/opnsensemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every OPNSense MCP Server tool call.

Deterministic rules across all 196 OPNSense MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

196 OPNSense MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.