detect_dynamic_code_risk — Garita MCP MCP Tool
detect_dynamic_code_risk
(detect dynamic code risk) is one of 30 tools on the
Garita MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call detect_dynamic_code_risk from your client
- Claude Code Garita MCP detect_dynamic_code_risk run in your project directory
- Claude Desktop Garita MCP detect_dynamic_code_risk ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Garita MCP detect_dynamic_code_risk ~/.cursor/mcp.json
- VS Code Garita MCP detect_dynamic_code_risk .vscode/mcp.json
- Zed Garita MCP detect_dynamic_code_risk ~/.config/zed/settings.json
- Windsurf Garita MCP detect_dynamic_code_risk ~/.codeium/windsurf/mcp_config.json
- Cline Garita MCP detect_dynamic_code_risk ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Garita MCP detect_dynamic_code_risk ~/.gemini/settings.json
- Grok Garita MCP detect_dynamic_code_risk .mcp.json (in your project root)
- ChatGPT Garita MCP detect_dynamic_code_risk Settings → Connectors → Advanced → Developer mode
- Claude.ai Garita MCP detect_dynamic_code_risk Settings → Connectors → Add custom connector
- LangChain Garita MCP detect_dynamic_code_risk pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http garita-mcp https://garita-mcp-server.onrender.com/mcpOther tools on this server
- audit_mcp_server
- simulate_approval
- detect_poisoned_tool_descriptions
- check_known_vulnerabilities
- detect_tool_rug_pull
- detect_poisoned_config_files
- check_package_authenticity
- detect_memory_poisoning
- detect_ssrf_risk
- detect_path_traversal_risk
- detect_command_injection_risk
- detect_sql_injection_risk
- detect_token_passthrough_risk
- detect_hardcoded_secrets_risk
- detect_insecure_deserialization_risk
- detect_toxic_flow_risk
- detect_ssti_risk
- detect_dns_rebinding_risk
- detect_missing_auth_risk
- detect_mcp_stdio_launch_risk
- detect_redos_risk
- detect_session_hijack_risk
- detect_oauth_audience_confusion_risk
- detect_unbounded_allocation_risk
- detect_cross_client_leak_risk
- detect_sampling_hijack_risk
- detect_output_schema_ssrf_risk
- detect_excessive_agency_risk
- detect_call_spoofing_risk
This list was read from the server itself, by connecting to it and calling tools/list on 14 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.