get_attack_status — Mitigant MCP Tool Read-only
get_attack_status
(get attack status) is one of 12 tools on the
Mitigant
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_attack_status from your client
- Claude Code Mitigant get_attack_status run in your project directory
- Claude Desktop Mitigant get_attack_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Mitigant get_attack_status ~/.cursor/mcp.json
- VS Code Mitigant get_attack_status .vscode/mcp.json
- Zed Mitigant get_attack_status ~/.config/zed/settings.json
- Windsurf Mitigant get_attack_status ~/.codeium/windsurf/mcp_config.json
- Cline Mitigant get_attack_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Mitigant get_attack_status ~/.gemini/settings.json
- Grok Mitigant get_attack_status .mcp.json (in your project root)
- ChatGPT Mitigant get_attack_status Settings → Connectors → Advanced → Developer mode
- Claude.ai Mitigant get_attack_status Settings → Connectors → Add custom connector
- LangChain Mitigant get_attack_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mitigant-mcp https://mcp.mitigant.io/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 5 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.