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