Integrations and access rules
Agents reach other systems through integrations:
- MCP servers, with OAuth or an API key. Their tools appear in the agent.
- APIs (REST connections). Operations imported from an OpenAPI document
appear as tools of the
act-apisMCP server. - Package registries and code hosts (npm, PyPI, GitHub, Go modules).
- DELEGATE itself as the built-in DELEGATE MCP server: tasks, change sets, knowledge and agents.
Credentials stay in DELEGATE. The egress proxy adds them to each call and records it in the audit log.
Access rules
Section titled “Access rules”Each integration of an agent has rules, checked for every request:
- APIs: by method and path, for example
POST /projects/*. The default: reads are allowed, everything else needs a change set. - MCP servers: by tool, for example
delete_*. The default: every tool is allowed.
Each rule says Allow, Deny or Change set required. The first matching rule wins.
Organization policy
Section titled “Organization policy”People who manage agents decide which package registries and code hosts may be granted at all (Egress audit page, Egress policy).