arp_discovery

Perform ARP discovery on the specified target with optional custom arguments.

SERVERNmapMCP SOURCE0xpratikpatil/nmapmcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xpratikpatil-nmapmcp/arp-discovery.md

WHAT IT DOES

What arp_discovery does on NmapMCP

AI agents invoke arp_discovery to trigger actions in NmapMCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why arp_discovery is rated High

ARP discovery is an active network reconnaissance operation that sends packets to external targets. It falls under Execute because it triggers external network operations whose effects depend on the target argument.

From the tool's definition 'Perform ARP discovery on the specified target' — actively sends ARP packets to enumerate live hosts on a network segment

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs arp_discovery safely

PolicyLayer is an MCP gateway: it sits between your AI agents and NmapMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For arp_discovery, this is the rule to start with:

arp_discovery Rate-limited

arp_discovery stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "arp_discovery": {
      "limits": [
        {
          "counter": "arp_discovery_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about arp_discovery

What does the arp_discovery tool do? +

Perform ARP discovery on the specified target with optional custom arguments. It is categorised as a Execute tool in the NmapMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on arp_discovery? +

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

What risk level is arp_discovery? +

arp_discovery is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit arp_discovery? +

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

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

arp_discovery is provided by the Nmap MCP server (0xpratikpatil/nmapmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nmap, and thousands of servers like it.

This server

All 15 Nmap tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →