Add Shrike action governance recipe (nemoclaw-community partner catalog) - #6
Open
Habirua wants to merge 1 commit into
Open
Add Shrike action governance recipe (nemoclaw-community partner catalog)#6Habirua wants to merge 1 commit into
Habirua wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the Shrike action-governance recipe under Agent Recipes.
It is a partner recipe in NVIDIA's nemoclaw-community catalog (merged after maintainer security review): an in-sandbox
before_tool_callplugin that evaluates each tool call — shell commands, SQL, file writes, web requests — against server-side policy before execution, returning allow / warn / require_approval / block. OpenShell contains where the agent can act; this governs what a specific action is. The recipe README is explicit that it is defense-in-depth inside the sandbox, not an independent security boundary — the OpenShell egress policy and credential provider remain the independent controls.Tested against the published recipe as merged; setup and requirements are in the recipe README.