registry_get_usb_history

THE RISK

Low Risk

Why registry_get_usb_history needs a policy

This tool queries and retrieves USB device history data from the Windows SYSTEM registry hive, which is a read-only forensic analysis operation. Registry reads do not modify system state, execute code, or cause irreversible changes.

From the tool's definition Tool name 'registry_get_usb_history' and description 'Get USB device history from SYSTEM hive' indicate retrieval of historical metadata from the Windows registry. No modification, deletion, or execution of code is performed.

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

POLICY

How to control registry_get_usb_history

PolicyLayer is an MCP gateway — it sits between your AI agents and Windows Forensics MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for registry_get_usb_history:

policy.json

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

registry_get_usb_history 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 Windows Forensics MCP Server — 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 Windows Forensics MCP Server tools

Execute die_analyze_file Analyze file with Detect It Easy (DiE). Execute remote_collect_artifacts Collect forensic artifacts from remote Windows system via WinRM. Supports password or pass Execute yara_scan_file Scan a file with YARA rules for malware detection. Uses bundled signature-base rules by de Read apmx_parse Parse Rohitab API Monitor capture file (.apmx64/.apmx86). Read build_timeline Build comprehensive forensic timeline from multiple artifact sources (MFT, USN Journal, Pr Read disk_parse_amcache Parse Amcache.hve to extract program execution evidence with SHA1 hashes, file paths, and Read disk_parse_mft Parse $MFT (Master File Table) for file metadata, NTFS alternate Read disk_parse_prefetch Parse Windows Prefetch files to determine program execution history, run counts, and last

All 61 Windows Forensics MCP Server 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 registry_get_usb_history

What does the registry_get_usb_history tool do? +

Get USB device history from SYSTEM hive. It is categorised as a Read tool in the Windows Forensics MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on registry_get_usb_history? +

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

What risk level is registry_get_usb_history? +

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

Can I rate-limit registry_get_usb_history? +

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

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

registry_get_usb_history is provided by the Windows Forensics MCP Server MCP server (x746b/winforensics-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Windows Forensics MCP Server tool call.

Start from Windows Forensics MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →