Collect a forensic investigation package from a device containing system information, logs, and diagnostic data. Requires MCP.Admin role.
AI agents invoke collect_investigation_package to trigger actions in Response MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an active forensic collection operation on a remote device, executing an investigation package collection that gathers system information, logs, and diagnostic data. It is not a passive read — it initiates an agent-driven action on the endpoint. It does not delete data (not Destructive) or move money (not Financial), but it does execute an external operation with real effects on the target device.
From the tool's definition 'Collect a forensic investigation package from a device containing system information, logs, and diagnostic data'
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access collect_investigation_package gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Response MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for collect_investigation_package:
{
"version": "1",
"default": "deny",
"tools": {
"collect_investigation_package": {
"limits": [
{
"counter": "collect_investigation_package_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} collect_investigation_package stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Collect a forensic investigation package from a device containing system information, logs, and diagnostic data. Requires MCP.Admin role. It is categorised as a Execute tool in the Response MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Response MCP Server MCP server in PolicyLayer and add a rule for collect_investigation_package: 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 Response MCP Server. Nothing to install.
collect_investigation_package is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the collect_investigation_package 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 collect_investigation_package. 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.
collect_investigation_package is provided by the Response MCP Server MCP server (markolauren/responsemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Response 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.
23 Response MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.