scan_log_for_attacks — LogTriage MCP Tool
scan_log_for_attacks
(scan log for attacks) is one of 7 tools on the
LogTriage
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call scan_log_for_attacks from your client
- Claude Code LogTriage scan_log_for_attacks run in your project directory
- Claude Desktop LogTriage scan_log_for_attacks ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor LogTriage scan_log_for_attacks ~/.cursor/mcp.json
- VS Code LogTriage scan_log_for_attacks .vscode/mcp.json
- Zed LogTriage scan_log_for_attacks ~/.config/zed/settings.json
- Windsurf LogTriage scan_log_for_attacks ~/.codeium/windsurf/mcp_config.json
- Cline LogTriage scan_log_for_attacks ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI LogTriage scan_log_for_attacks ~/.gemini/settings.json
- Grok LogTriage scan_log_for_attacks .mcp.json (in your project root)
- ChatGPT LogTriage scan_log_for_attacks Settings → Connectors → Advanced → Developer mode
- Claude.ai LogTriage scan_log_for_attacks Settings → Connectors → Add custom connector
- LangChain LogTriage scan_log_for_attacks pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http logtriage https://api.logtriage.app/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.