MCP tools bypassed our agent's approval gate—here's the fail-closed fix

GapNew4766 · reddit · 2026-10-13

Atomic Agent, an MIT-licensed agent that doubles as an MCP client, disclosed an embarrassing hole: built-in file writes and shell commands required user approval, but the same writes proxied through an MCP server executed silently. The culprit was the default trust: "approvalgated" config, which read like consent but was only a scheduling constraint. An outside contributor found it in v0.3.1 (issue #132); the fix landed Aug 31.

The new rule

Composio integration

Instead of stuffing thousands of schemas into a local model's prompt, one POST to Composio's tool router returns a Streamable HTTP MCP URL exposing four meta-tools: SEARCHTOOLS and GETTOOLSCHEMAS (read-only, run free) vs MANAGECONNECTIONS and MULTIEXECUTETOOL (mutating, ask first). Caveats: requires your own Composio key, and it's hosted, so OAuth tokens flow through Composio's servers.

Migration & extras

atomic-agent import claude-code picks up MCP servers (they live in /.claude., not the directory), skills, memory, and sessions, with --dry-run and explicit --migrate-secrets for API keys. In Fusion mode, the planner treats every MCP tool as mutating regardless of annotations.

Original post →

More from coding & agent

coding & agent channel →