Skip to content

Consider a --strict mode to enforce deny-by-default permissions to both engine and MCP servers #234

Description

@Mossaka

The current enforcement of the network egress control for the engine is the following:

  1. If permissions.network is not there, allow all traffic.
  2. If permissions.network is there, and allowed list is empty, deny all traffic
  3. If permissions.network is there, and allowed list is non-empty, deny traffic except the domains in the whitelist.

This makes sense since I've been very careful for not breaking any existing workflows, but there is a big downside to this current approach. That is, if permissions is not set, all traffic are bypassing security policies, which is against the zero trust principles.

I am proposing adding a --strict mode to enable deny-by-default for all.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

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