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