Skip to content
Awaken

Enable Tool Permission HITL

Tool permission HITL is a governance workflow: decide which tools may run without review, which must ask a human, and which should never be exposed. Use the Admin Console first so the policy is visible next to the agent draft.

What you click

Section titled “What you click”
Agent editor Plugins tab with Permissions, Reminders, deferred_tools, and a Permission rules config card.
Agent editor: enable the permission plugin and edit rules for the draft.
Agent editor Tools tab showing allowed web_search, read_document, filesystem/read_file, summarize, and excluded delete_file.
Agent Tools tab: confirm which tools are exposed before adding permission rules.
  1. Open Tools and identify the sensitive tool ids.
  2. Open Agents and choose the agent.
  3. On Tools, expose only the tools this agent should know about.
  4. On Plugins, enable the permission plugin.
  5. Add rules:
    • Allow for safe read-only tools.
    • Ask for tools that can spend money, write files, call external systems, or reveal sensitive data.
    • Deny for tools this agent must never call.
  6. Click Validate.
  7. Preview one prompt that should run without asking and one that should suspend for review.
  8. Save when both paths are correct.

Rule checklist

Section titled “Rule checklist”
QuestionUI check
Does the agent need to see this tool at all?Tools tab allow/exclude selection
Should the tool be available but reviewed?Plugins → Permission → Ask
Should the tool disappear from the effective catalog?Plugins → Permission → Deny or exclude it in Tools
Are argument-sensitive rules needed?Add a rule that matches the tool arguments, then preview that exact case
Did the policy change after save?History and Audit Log

Verify and operate

Section titled “Verify and operate”
Agent editor History tab with update/create events and Restore actions.
Use History to review permission-rule changes and restore prior policy.

After saving, run a real task or eval fixture that tries the sensitive tool. A correct Ask rule should suspend for human review in your client/HITL surface. If the model can still call a tool that should be blocked, tighten the Tools allowlist and the permission rule together.

API references for automation

Section titled “API references for automation”