AI agents call find_device_by_name 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.
This tool performs a search/lookup operation based on a hostname pattern. It retrieves information about devices without side effects, state changes, or execution of commands. This is a typical Read category operation. The severity is low because hostname lookups pose minimal security risk—they are informational queries that do not alter firewall configuration, trigger network operations, or commit resources.
From the tool's definition Tool name 'find_device_by_name' and description 'Find devices by hostname pattern' indicate a query operation that retrieves device information without modifying or executing actions on network infrastructure.
Documented attack patterns abuse exactly the kind of access find_device_by_name 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 find_device_by_name:
{
"version": "1",
"default": "deny",
"tools": {
"find_device_by_name": {}
}
}find_device_by_name is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Find devices by hostname pattern. It is categorised as a Read tool in the OPNSense MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OPNSense MCP Server MCP server in PolicyLayer and add a rule for find_device_by_name: 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.
find_device_by_name is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the find_device_by_name 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.
Set action: deny in the PolicyLayer policy for find_device_by_name. 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.
find_device_by_name 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.
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.