module_exports

THE RISK

Low Risk

Why module_exports needs a policy

The tool itself performs a read-only operation: listing exported functions from a module's EAT. However, it operates in a high-privilege context (DMA access, process memory inspection) where an AI agent could leverage module export information to chain with other tools like memory_dump or memory_patch for reconnaissance and subsequent exploitation.

From the tool's definition Tool name 'module_exports' and description 'List all exported functions (Export Address Table) from a loaded module' indicate data retrieval without modification.

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

POLICY

How to control module_exports

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 module_exports:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "module_exports": {}
  }
}

module_exports is read-only, so it stays allowed — but 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.

CAP 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 →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about module_exports

What does the module_exports tool do? +

List all exported functions (Export Address Table) from a loaded module. It is categorised as a Read tool in the Nevercheese Pcileech Memprocfs MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on module_exports? +

Register the Nevercheese Pcileech Memprocfs MCP server in PolicyLayer and add a rule for module_exports: 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 module_exports? +

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

Can I rate-limit module_exports? +

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

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

module_exports 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 →