Search API calls by parameter value in an APMX capture.
AI agents call apmx_search_params 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 tool performs a read-only search operation on forensic data (APMX captures). It retrieves and queries information without side effects, matching the definition of 'Read'. The forensics context does not elevate severity since the tool itself only searches existing data rather than executing code or modifying systems.
From the tool's definition Tool name 'apmx_search_params' combined with description 'Search API calls by parameter value in an APMX capture' indicates a query/search operation on forensic artifacts. No modification, deletion, execution, or financial operations are implied.
Documented attack patterns abuse exactly the kind of access apmx_search_params 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 apmx_search_params:
{
"version": "1",
"default": "deny",
"tools": {
"apmx_search_params": {}
}
}apmx_search_params 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.
Search API calls by parameter value in an APMX capture. 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 apmx_search_params: 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.
apmx_search_params 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 apmx_search_params 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 apmx_search_params. 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.
apmx_search_params 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.