Skip to content
Browse documentation

Integrating CrewAI

Wrap tools at crew construction so every agent in the crew — not just the one you tested — inherits the same governed boundary.

A crew is several agents with different roles, often at different privilege levels. Wrapping at crew construction means a new role added to the crew is governed by default, rather than governed only if someone remembers to wrap it.

Install

TerminalShell
$ pip install cirvix

Wrap per role

crew.pyPython
from crewai import Agent, Crewfrom cirvix.integrations.crewai import guard researcher = Agent(    role="Researcher",    tools=guard.wrap(research_tools, agent="crew-researcher", policy_dir="./policies"),) engineer = Agent(    role="Engineer",    tools=guard.wrap(engineer_tools, agent="crew-engineer", policy_dir="./policies"),) crew = Crew(agents=[researcher, engineer], tasks=tasks)crew.kickoff()

crew-researcher and crew-engineer are separate agent identities with separate scopes — a policy can permit the researcher read-only access and the engineer a held write, in the same policy set.

Note
When one crew member delegates work to another, that hop is exactly what the A2A Gateway governs: delegated scope can only narrow, never regain privilege the caller didn't have.
Edit this page on GitHub
Was this page helpful?