incident_response_evidence_collector
As a CTO, gather forensic evidence (logs, network flows, MITRE TTPs) from public breach reports and threat intelligence sources to support incident response post-mortems. Inputs include incident identifiers, date ranges, or MITRE technique IDs. Outputs structured evidence with attack patterns, in...
This record as markdown: /tools/io-github-getgapup-gapup-mcp/incident-response-evidence-collector.md
What incident_response_evidence_collector does on Gapup Mcp
AI agents call incident_response_evidence_collector to retrieve information from Gapup Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
async | boolean | — | If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti |
date_range | object | — | |
incident_id | string | Yes | Unique identifier for the incident (e.g., CVE, GitHub Advisory ID) |
mitre_technique_ids | array | — | List of MITRE ATT&CK technique IDs (e.g., T1059) |
include_network_flows | boolean | — |
Parameters from the server's own tool schema.
Why incident_response_evidence_collector is rated Low
The tool retrieves and aggregates publicly available threat intelligence, breach reports, and MITRE ATT&CK data. It is purely a read/query operation with no side effects on external systems. Severity is medium because the aggregated forensic evidence (IOCs, attack patterns, TTPs) could be sensitive and potentially misused to inform offensive operations if accessed by a malicious actor.
From the tool's definition gather forensic evidence (logs, network flows, MITRE TTPs) from public breach reports and threat intelligence sources
Attacks that exploit this kind of access
The rule that runs incident_response_evidence_collector safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gapup Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For incident_response_evidence_collector, this is the rule to start with:
incident_response_evidence_collector is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gapup Mcp, apply this rule, and every incident_response_evidence_collector call is checked against it from then on.
Questions about incident_response_evidence_collector
As a CTO, gather forensic evidence (logs, network flows, MITRE TTPs) from public breach reports and threat intelligence sources to support incident response post-mortems. Inputs include incident identifiers, date ranges, or MITRE technique IDs. Outputs structured evidence with attack patterns, indicators of compromise, and source references. — pass async:true REQUIRED to avoid x402 timeout. It is categorised as a Read tool in the Gapup Mcp MCP Server, which means it retrieves data without modifying state.
incident_response_evidence_collector accepts 5 parameters: async, date_range, incident_id, mitre_technique_ids, include_network_flows. Required: incident_id. The full parameter table on this page comes from the server's own tool schema.
Register the Gapup MCP server in PolicyLayer and add a rule for incident_response_evidence_collector: 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 Gapup Mcp. Nothing to install.
incident_response_evidence_collector 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 incident_response_evidence_collector 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 incident_response_evidence_collector. 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.
incident_response_evidence_collector is provided by the Gapup MCP server (https://mcp.gapup.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gapup, and thousands of servers like it.
This server
Across the catalogue