Skip to content
PERMISSION/PROTOCOL
← Integrations

Workflow integration guide

Protect the execution path around your coding agent.

Choose what you need to control: a change reaching a protected GitHub workflow, or a tool call sent through a configured MCP server.

Review Deploy Gate setup Walk through an approval

What setup requires.

  1. 01

    Select one repository and a protected merge or deployment workflow.

  2. 02

    Configure required checks, approvals, and the receipt requirement for that path.

  3. 03

    For MCP calls, evaluate MCP Guard separately on the configured server connection.

  4. 04

    Test alternate credentials, direct shell commands, changed commits, and administrator bypass.

Coverage and limits.

  • A GitHub check does not prevent local file edits or direct commands on a developer machine.
  • An MCP proxy covers its routed tool calls, not every action taken by the coding agent.
  • The configured enforcement boundary matters more than which coding agent authored the change.

Have a different execution path?

Bring the action, target system, and required evidence. We can assess the integration work before you commit to a rollout.

Discuss your workflow