intentfence_authorize_action — IntentFence Agent Action Firewall MCP Tool
intentfence_authorize_action
(intentfence authorize action) is one of 10 tools on the
IntentFence Agent Action Firewall
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call intentfence_authorize_action from your client
- Claude Code IntentFence Agent Action Firewall intentfence_authorize_action run in your project directory
- Claude Desktop IntentFence Agent Action Firewall intentfence_authorize_action ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor IntentFence Agent Action Firewall intentfence_authorize_action ~/.cursor/mcp.json
- VS Code IntentFence Agent Action Firewall intentfence_authorize_action .vscode/mcp.json
- Zed IntentFence Agent Action Firewall intentfence_authorize_action ~/.config/zed/settings.json
- Windsurf IntentFence Agent Action Firewall intentfence_authorize_action ~/.codeium/windsurf/mcp_config.json
- Cline IntentFence Agent Action Firewall intentfence_authorize_action ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI IntentFence Agent Action Firewall intentfence_authorize_action ~/.gemini/settings.json
- Grok IntentFence Agent Action Firewall intentfence_authorize_action .mcp.json (in your project root)
- ChatGPT IntentFence Agent Action Firewall intentfence_authorize_action Settings → Connectors → Advanced → Developer mode
- Claude.ai IntentFence Agent Action Firewall intentfence_authorize_action Settings → Connectors → Add custom connector
- LangChain IntentFence Agent Action Firewall intentfence_authorize_action pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http intentfence https://agentpass-protocol.rmalka06.chatgpt.site/api/mcpOther 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.