Intutic vs Zenity
Last reviewed: 2026-10-10
Intutic is the enforcement point inside the coding agent: a pre-execution gate decides each tool call in 36 of the 43 supported harnesses, with a policy proxy, an MCP governance proxy, a default-deny egress firewall, sandboxed execution behind it. It is open core. Zenity (zenity.io) secures AI agents across an organization: assistants such as Microsoft Copilot, ChatGPT Enterprise and Gemini, agents built on Foundry, Bedrock and Vertex, and, for coding and personal agents, native agent hooks and an MCP gateway that block or modify a tool call before it runs. Zenity covers the breadth of enterprise AI from one platform; Intutic goes deep on coding agents and agent frameworks, where they run.
Comparison
| Intutic | Zenity | |
|---|---|---|
| Where enforcement happens | At the tool call: native pre-execution hook gates in 18 of the 43 harnesses and in-process SDK gates in 17 agent frameworks; plus a request and response proxy, an MCP governance proxy, a host egress firewall (intutic enforce) and sandboxed execution (intutic exec --sandbox) | Native agent hooks (pre-tool blocking in Claude Code, Cursor and Codex) and its MCP gateway, which block or modify a tool call before it runs. Telemetry comes from OpenTelemetry and the hooks; Claude Enterprise connects through Anthropic's Compliance API. The vendor says no endpoint sensor is needed |
| Coding agents covered | 43 supported harnesses, including Claude Code, Codex, Cursor, GitHub Copilot, Windsurf, Cline, Roo Code, OpenCode and Goose, plus agent frameworks such as LangGraph, CrewAI and the OpenAI Agents SDK through an in-process gate | Claude Code, Claude Cowork, Codex, GitHub Copilot and Cursor are named on its coding-agents page; hooks for GitHub Copilot and Codex became generally available in August 2026 |
| Policy actions | Allow, warn, require approval (the call is refused and held for review; with a control plane, once a reviewer approves it the identical retry passes if the workspace has opted in, and with none it stays refused), block, redact, re-ask, and shadow mode that measures how often a rule would act | Block a tool call, redact output, or show guidance in the agent's chat; MCP allowlists set at build time. Rules run in Detect or Prevent mode, and each taint is marked as blocking or flag-only |
| When the policy layer fails | Hook gates fail closed on a crash or a malformed payload, and the proxy blocks by default when its policy service is unreachable. With no configuration, the gates block writes to their own hook files and settings, governance-bypass commands and secrets, and the proxy refuses rm -rf /, mkfs and similar operations in a model's code-execution tool call. The gates' destructive-command tier flags those commands rather than blocking them | Not documented |
| MCP governance | MCP governance proxy with a server registry, approvals and optional default-deny, approval holds, per-call identity, DLP, policy rules, anomaly detectors, trust-on-first-use pinning and tool-description poisoning detection | An MCP gateway behind one URL that allows, modifies or blocks each tool, per agent, user or team |
| Red teaming | — | No red-teaming product documented. Risky skills, files and code can be detonated in a sandbox |
| Source | Open core (MIT): the proxy, hook gates, MCP proxy, CLI and sync daemon | The platform's source is not published; Zenity released an open-source security framework for OpenClaw in March 2026, with no licence stated |
Where Zenity is stronger
- Breadth beyond coding agents. One platform covers enterprise assistants (Microsoft Copilot, ChatGPT Enterprise, Gemini) and agents built on Foundry, Bedrock and Vertex alongside coding agents. Intutic governs coding agents and agent frameworks.
- Nothing on the endpoint. The vendor says its coding-agent coverage needs no endpoint sensor. Every Intutic enforcement point runs on the machine, in the CI job or beside the service.
- Policy drafted and tested for you. An AI assistant in Zenity drafts a rule and tests it against recent activity; rules can also be managed as code through a CLI. Intutic's Policy Guardrails start from the policy documents you already have, cite the passage behind each rule, and prove it in shadow mode before a person promotes it.
- Detonation of suspect artefacts. Zenity runs risky skills, files and code in a sandbox to see what they do. Intutic's sandbox (
intutic exec --sandbox) contains the agent's own execution. - Per-team MCP tool policy behind one URL. Its MCP gateway can modify a tool call as well as allow or block it, per agent, user or team.
When to choose Intutic
- Your agents are coding agents and agent frameworks, such as Windsurf, Cline, Goose or LangGraph alongside Claude Code and Cursor, and you want each tool call decided before it runs.
- You want risky calls held for approval rather than only allowed or blocked.
- You want to read the code that blocks a call.
- You want an egress firewall and a sandbox so an agent cannot route around governance.
When to choose Zenity
- You need to secure enterprise assistants and agent platforms, such as Microsoft Copilot and ChatGPT Enterprise, from the same console as your coding agents.
- You want coding-agent coverage without installing a sensor on developer machines.
- You do not need to run the platform on your own infrastructure.
Use them together
Zenity can cover the enterprise assistants and agent platforms while Intutic gates the coding agents' tool calls inside each harness and contains their network access. Each governs a different part of the organization's AI use.