Repository navigation
Run Firewall on the no-code MCP path for Codex, Grok Bot, and any MCP client #5263
salem221094
started this conversation in
Feature request
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Firewall is only attached when a session is created in code with hooks. The docs say before_execute and after_execute do not run when a client uses session MCP, because the client talks to Composio’s server and bypasses the SDK.
I use Codex and Grok Bot. Both already connect to Composio through the hosted MCP URL or the Grok Bot Composio plugin, with no code. I need the same natural-language Firewall rules to apply there.
Requested behavior:
Why this matters: the people who most need a safety check are using Codex, Grok Bot, Claude, and Cursor as MCP clients. Those clients cannot run Composio’s SDK hooks. A no-code toggle on the existing MCP connection would make Firewall usable without building an agent.
All reactions