export_policy — MCP Verify MCP Tool Read-only
export_policy
(export policy) is one of 22 tools on the
MCP Verify
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call export_policy from your client
- Claude Code MCP Verify export_policy run in your project directory
- Claude Desktop MCP Verify export_policy ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MCP Verify export_policy ~/.cursor/mcp.json
- VS Code MCP Verify export_policy .vscode/mcp.json
- Zed MCP Verify export_policy ~/.config/zed/settings.json
- Windsurf MCP Verify export_policy ~/.codeium/windsurf/mcp_config.json
- Cline MCP Verify export_policy ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MCP Verify export_policy ~/.gemini/settings.json
- Grok MCP Verify export_policy .mcp.json (in your project root)
- ChatGPT MCP Verify export_policy Settings → Connectors → Advanced → Developer mode
- Claude.ai MCP Verify export_policy Settings → Connectors → Add custom connector
- LangChain MCP Verify export_policy pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http verify https://verify.sentinelsignal.io/mcpOther tools on this server
- search
- fetch
- search_servers
- recommend_servers
- get_server_report
- compare_servers
- route_task
- decide_agent_call
- create_mandate
- get_evidence_pack
- compile_docs
- get_subscription_options
- get_gateway_options
- get_hosting_options
- list_agents
- get_agent
- score_agent
- explain_agent_risk
- list_high_risk_agents
- get_drift_report
- generate_remediation_plan
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.