Governance - GroundForge

The SDK reports the Agent’s tools to GroundForge. An administrator can then assign one action to each discovered tool: Allow, Observe, Review, or Block. Using the demo Agent:

User asks: What is the weather in Ottawa?
Agent selects: get_weather(city="Ottawa")
GroundForge checks: the rule for get_weather

Action	What the user sees	Does `get_weather` run?
Allow	Normal Agent response	Yes
Observe	Normal Agent response	Yes, with a highlighted decision in the Trace
Review	A configured review message while an operator decides	Only after approval
Block	A configured policy response	No

How the SDK applies the decision

The Channel request reaches the running external Agent.
The Agent selects get_weather.
The SDK checks the Gateway decision before calling the original Python function.
Allow and Observe continue immediately. Review creates an Operator Task. Block stops the call.
The result and decision are included in the request Trace.

For Review, an operator opens Operator Tasks in GroundForge and approves or rejects the exact requested call. A rejection does not call the tool. For a Block test, open the Trace and confirm that get_weather is marked as not executed and has no tool output.

Example

Set get_weather to Review, send the same weather question, and verify the tool does not run until the Operator Task is approved. Follow Request Review for the exact steps.

Last modified on July 27, 2026

Related topics

Governance Operator Tasks Gateways Traces