get_detection_rules — Stackcut MCP Tool Read-only
get_detection_rules
(get detection rules) is one of 20 tools on the
Stackcut
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_detection_rules from your client
- Claude Code Stackcut get_detection_rules run in your project directory
- Claude Desktop Stackcut get_detection_rules ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Stackcut get_detection_rules ~/.cursor/mcp.json
- VS Code Stackcut get_detection_rules .vscode/mcp.json
- Zed Stackcut get_detection_rules ~/.config/zed/settings.json
- Windsurf Stackcut get_detection_rules ~/.codeium/windsurf/mcp_config.json
- Cline Stackcut get_detection_rules ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Stackcut get_detection_rules ~/.gemini/settings.json
- Grok Stackcut get_detection_rules .mcp.json (in your project root)
- ChatGPT Stackcut get_detection_rules Settings → Connectors → Advanced → Developer mode
- Claude.ai Stackcut get_detection_rules Settings → Connectors → Add custom connector
- LangChain Stackcut get_detection_rules pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http stackcut https://stackcut.io/mcpOther tools on this server
- search_recipes
- get_recipe
- find_alternatives
- get_build_packet
- search_workflow_recipes
- get_workflow_recipe
- leaderboard
- audit_stack
- get_usage_questions
- start_audit
- list_categories
- get_my_plan
- choose_stack
- plan_stack_from_spec
- list_stack_jobs
- get_exit_plan
- search_exits
- report_exit_outcome
- report_outcome
This list was read from the server itself, by connecting to it and calling tools/list on 2 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.