Detect injection/evasion/persistence API patterns from PE imports.
AI agents call api_detect_patterns to retrieve information from Windows Forensics MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a forensic analysis tool that queries/parses PE import metadata to identify suspicious API call patterns indicative of malicious behavior. It performs static analysis and pattern matching on read-only data structures (PE headers, import tables). The tool does not execute code, modify data, delete anything, or trigger external operations — it only retrieves and analyzes forensic artifacts.
From the tool's definition Tool description states 'Detect injection/evasion/persistence API patterns from PE imports' — it analyzes and detects patterns in already-collected PE (Portable Executable) import data without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access api_detect_patterns gives an agent:
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 api_detect_patterns:
{
"version": "1",
"default": "deny",
"tools": {
"api_detect_patterns": {}
}
}api_detect_patterns is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Detect injection/evasion/persistence API patterns from PE imports. It is categorised as a Read tool in the Windows Forensics MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Windows Forensics MCP Server MCP server in PolicyLayer and add a rule for api_detect_patterns: 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.
api_detect_patterns is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the api_detect_patterns 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.
Set action: deny in the PolicyLayer policy for api_detect_patterns. 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.
api_detect_patterns 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.
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.
Free to start. No card required.
61 Windows Forensics MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.