Bewize Request Demo

Agent policy

How do I manage agent policy in Hermes Hub?

Manage agent policy in Hermes Hub by reviewing the effective hub and tenant policy, changing only accepted policy fields, and verifying the resulting runtime behavior and evidence. The public API exposes hub-wide and tenant-specific policy surfaces so operations can define capability boundaries without treating policy as an undocumented prompt.

Read the API contract Review security

A governed policy workflow

Pair every policy change with scope, ownership, and verification.

Identify scope

Determine whether the change applies hub-wide or to one tenant override.

Apply accepted controls

Use the documented policy surface and keep credentials and private runtime state outside ordinary content.

Verify runtime evidence

Review access state, run history, schedules, and redacted metrics after the change.

Policy references

Hermes Hub agent policy FAQ

Should policy be managed only at the hub-wide level?
Not necessarily. The public contract includes hub-wide policy and tenant agent-policy overrides, so scope should match the operational requirement.
What should follow a policy change?
Verify the affected tenant access state, runtime behavior, run history, schedules, and available redacted operational evidence.
Does a policy API guarantee secure behavior?
No. It is a control surface that should be evaluated with the rest of the tenant isolation, secret, access, and evidence model.

Design agent policy controls

Discuss hub-wide and tenant-scoped policy boundaries for managed Hermes Agent runtimes.

+1 332 2081410
[email protected]

Architecture conversation

Tell us what your team needs to control

Share your deployment boundary, number of agents, work surfaces, and governance requirements. We will reply by email to arrange a focused technical discussion.

Email the Bewize team

This opens your email application. Read our Privacy Policy.