SDK integration

Running a LangGraph or custom Python agent? Route its tool calls through the Guardyx SDK to get the same control plane — policy, approvals, audit, observability — around code you already have.

Wrap a tool call

# before
tool.send_email(payload)

# after
guardyx.execute("send_email", payload)

The guardyx.execute(...) call performs the same action, but only after policy and any required approvals pass. Blocked or pending calls surface in the portal with the full payload and decision context.

When to choose the SDK vs MCP

• MCP is the primary path when your agent runs inside an MCP client — it’s a config change with no code edits. See the Quickstart.
• SDK is the right path when you own the agent code and want explicit control over which calls are governed.