device_disconnect

THE RISK

Low Risk

Why device_disconnect needs a policy

This tool disconnects from a hardware device (DMA/FPGA), releasing it for other use. It does not read, write, execute code, delete data, or move money. It is a session/connection management operation. The main risk is denial of service (disrupting ongoing memory operations), but it doesn't directly cause data loss or irreversible damage — it simply ends the device connection.

From the tool's definition Disconnect from the DMA/FPGA device, freeing it for external use.

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

POLICY

How to control device_disconnect

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "device_disconnect": {
      "limits": [
        {
          "counter": "device_disconnect_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

device_disconnect gets a rate cap, and everything else on the server is denied unless you say otherwise.

Create a free account and register Nevercheese Pcileech Memprocfs — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

SET A RULE FOR THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Nevercheese Pcileech Memprocfs tools

Execute device_reconnect Reconnect to the DMA/FPGA device after a previous device_disconnect. Execute benchmark Measure DMA read/write throughput in MB/s. Use this to verify the FPGA device Execute fpga_config Read or write the FPGA Execute memory_write Write bytes to the target system Execute signature_resolve Find a byte pattern and resolve the operand to a target address — all in one step. Execute tlp_send Send and/or receive raw PCIe Transaction Layer Packets (TLPs). FPGA devices only. Write memory_patch NOT YET IMPLEMENTED. Signature-based patching (.sig files) is a pcileech CLI feature Read aob_scan Array-of-bytes pattern scan with ?? wildcard support in a process

All 37 Nevercheese Pcileech Memprocfs tools →

Other tools on other servers

Android Forensics ADB MCP Server generate_app_analysis_report Ethereum Tools add Math MCP Server complex_analysis_suite Crypto_MCP aes_encrypt

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Tool risk categories → How PolicyLayer classifies MCP tools by what they can do.
MCP tool → What an MCP tool is and how clients discover and call it.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about device_disconnect

What does the device_disconnect tool do? +

Disconnect from the DMA/FPGA device, freeing it for external use. It is categorised as a Other tool in the Nevercheese Pcileech Memprocfs MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on device_disconnect? +

Register the Nevercheese Pcileech Memprocfs MCP server in PolicyLayer and add a rule for device_disconnect: 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 Nevercheese Pcileech Memprocfs. Nothing to install.

What risk level is device_disconnect? +

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

Can I rate-limit device_disconnect? +

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

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

device_disconnect is provided by the Nevercheese Pcileech Memprocfs MCP server (neverdecel/nevercheese-pcileech-memprocfs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Nevercheese Pcileech Memprocfs tool call.

Start from Nevercheese Pcileech Memprocfs, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →