breach_response_steps — Teollimi MCP Tool
breach_response_steps
(breach response steps) is one of 5 tools on the
Teollimi
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call breach_response_steps from your client
- Claude Code Teollimi breach_response_steps run in your project directory
- Claude Desktop Teollimi breach_response_steps ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Teollimi breach_response_steps ~/.cursor/mcp.json
- VS Code Teollimi breach_response_steps .vscode/mcp.json
- Zed Teollimi breach_response_steps ~/.config/zed/settings.json
- Windsurf Teollimi breach_response_steps ~/.codeium/windsurf/mcp_config.json
- Cline Teollimi breach_response_steps ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Teollimi breach_response_steps ~/.gemini/settings.json
- Grok Teollimi breach_response_steps .mcp.json (in your project root)
- ChatGPT Teollimi breach_response_steps Settings → Connectors → Advanced → Developer mode
- Claude.ai Teollimi breach_response_steps Settings → Connectors → Add custom connector
- LangChain Teollimi breach_response_steps pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http teollimi https://teollimi.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 11 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.