Skip to content

Governance layer for flow execution — scoped delegation, signed receipts, multi-tenant isolation #6169

@aeoess

Description

@aeoess

Flowise makes it easy to build agent workflows visually. The missing piece: when those workflows execute actions with real consequences (API calls, database writes, payments, data access), there's no governance layer between the flow and the execution.

For enterprise deployments, this means:

  • A flow built by one team member can access tools it shouldn't. There's no scoped delegation saying "this flow can read from the CRM but not write."
  • When a flow does something unexpected in production, the only evidence is logs. There's no signed, tamper-evident receipt proving what the flow was authorized to do.
  • Flows can't delegate to sub-agents with narrower permissions. A parent flow and its children all share the same permission level.

Here's how governance wraps a Flowise tool execution:

import { governMCPToolCall } from 'agent-passport-system'

// Each deployed flow gets an Ed25519 identity and scoped delegation
// Admin creates: "support-flow can use crm:read and email:send, nothing else"

const result = await governMCPToolCall(
  { name: 'database_write', arguments: { table: 'users', data: payload } },
  async (args) => originalTool.execute(args),  // the actual tool
  { passport: flowPassport, delegation: flowDelegation, privateKey: flowKey }
)

if (!result.permitted) {
  // database_write not in scope — blocked before execution
  // result.receipt is signed proof of the denial
}
// If permitted: result.receipt proves the action was authorized

This integrates at the tool execution layer. Every tool call in the flow passes through governance. The delegation defines what the flow can do. The receipt proves what it actually did.

For multi-tenant Flowise deployments: each tenant gets their own delegation scope. Tenant A's flows can't access Tenant B's tools, enforced cryptographically rather than by application logic.

npm install agent-passport-system (v1.36.2, Apache-2.0). Self-service gateway at aeoess.com/portal.html — free tier covers 3 flows and 1,000 evaluations/month.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions