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