clean_up_attack — Mitigant MCP Tool
clean_up_attack
(clean up attack) 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 clean_up_attack from your client
- Claude Code Mitigant clean_up_attack run in your project directory
- Claude Desktop Mitigant clean_up_attack ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Mitigant clean_up_attack ~/.cursor/mcp.json
- VS Code Mitigant clean_up_attack .vscode/mcp.json
- Zed Mitigant clean_up_attack ~/.config/zed/settings.json
- Windsurf Mitigant clean_up_attack ~/.codeium/windsurf/mcp_config.json
- Cline Mitigant clean_up_attack ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Mitigant clean_up_attack ~/.gemini/settings.json
- Grok Mitigant clean_up_attack .mcp.json (in your project root)
- ChatGPT Mitigant clean_up_attack Settings → Connectors → Advanced → Developer mode
- Claude.ai Mitigant clean_up_attack Settings → Connectors → Add custom connector
- LangChain Mitigant clean_up_attack 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.