Low Risk

find_device_by_mac

Find device by MAC address

How to control find_device_by_mac ↓

AI agents call find_device_by_mac 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

This tool performs a read-only lookup in the OPNSense firewall's device database using a MAC address as the search parameter. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal—an attacker could discover which devices are connected to the network, but cannot take further action without additional tools. This is a classic Read operation.

From the tool's definition Tool name 'find_device_by_mac' and description 'Find device by MAC address' indicate a query/lookup operation that retrieves information about a network device without modifying any state or triggering side effects.

Documented attack patterns abuse exactly the kind of access find_device_by_mac 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_mac:

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

find_device_by_mac 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 find_device_by_mac tool do? +

Find device by MAC address. 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 find_device_by_mac? +

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

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

Can I rate-limit find_device_by_mac? +

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

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

find_device_by_mac 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.