custom_scapy_filter · Network MCP Server MCP: Risk & Policy

WHAT IT DOES

What custom_scapy_filter does on Network MCP Server

AI agents invoke custom_scapy_filter to trigger actions in Network MCP Server. 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.

WHY IT NEEDS A POLICY

Why custom_scapy_filter needs a policy

Scapy is a powerful Python network tool capable of crafting and injecting arbitrary packets, running custom scripts, and performing deep packet inspection. A 'custom_scapy_filter' tool almost certainly executes user-supplied filter expressions or code against network traffic, representing high execution risk.

From the tool's definition Tool name 'custom_scapy_filter' implies execution of custom Scapy (Python packet manipulation library) filters/scripts. Scapy allows arbitrary packet crafting, network injection, sniffing, and code execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

custom_scapy_filter Rate-limited

custom_scapy_filter 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": {
    "custom_scapy_filter": {
      "limits": [
        {
          "counter": "custom_scapy_filter_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Network MCP Server, so you can run agents against it safely.

FAQ

Questions about custom_scapy_filter

What does the custom_scapy_filter tool do? +

custom_scapy_filter. It is categorised as a Execute tool in the Network MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on custom_scapy_filter? +

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

What risk level is custom_scapy_filter? +

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

Can I rate-limit custom_scapy_filter? +

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

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

custom_scapy_filter is provided by the Network MCP Server MCP server (labeveryday/network-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.