incident_response — AgentAegis MCP Prompt

incident_response is one of 4 prompts on the AgentAegis MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke incident_response from your client

• Claude Code AgentAegis Prompt/incident_response run in your project directory
• Claude Desktop AgentAegis Prompt/incident_response ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor AgentAegis Prompt/incident_response ~/.cursor/mcp.json
• VS Code AgentAegis Prompt/incident_response .vscode/mcp.json
• Zed AgentAegis Prompt/incident_response ~/.config/zed/settings.json
• Windsurf AgentAegis Prompt/incident_response ~/.codeium/windsurf/mcp_config.json
• Cline AgentAegis Prompt/incident_response ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI AgentAegis Prompt/incident_response ~/.gemini/settings.json
• Grok AgentAegis Prompt/incident_response .mcp.json (in your project root)
• ChatGPT AgentAegis Prompt/incident_response Settings → Connectors → Advanced → Developer mode
• Claude.ai AgentAegis Prompt/incident_response Settings → Connectors → Add custom connector
• LangChain AgentAegis Prompt/incident_response pip install langchain-mcp-adapters

Other prompts on this server

• security_audit
• pre_install_trust_check
• compliance_readiness

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.