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