Permission policies
Set each tool to allow, ask, or deny.
terminal
files
secrets
Security and access control
Control what every agent can do before it runs.
Herm lets teams set tool permissions, approval rules, agent roles, and scoped vault access so production agents only reach the systems they are allowed to use.
access-control.console
Role policy matrix
filesshellvault
readonly
allowdenydenyoperator
allowaskaskadmin
allowallowaskrequest
policy
decision
Approval queue
shell commandneeds approval
crm lookupauto allowed
billing writeblocked
Vault access
resolved only after policy passes
01 / ACCESS CONTROLS
Role boundaries
Start sessions with the right access level.
readonly
operator
admin
Approval checkpoints
Pause sensitive actions before they run.
tool requestedpaused
human approvalrequired
action runsapproved
Scoped credentials
Attach vault access only where it belongs.
crm vault
slack vault
billing vault
02 / EXAMPLES
Use access controls wherever an agent can touch customer systems.
Set the role, tools, approval policy, and credentials for the situation the agent is serving.
Customer support agent
Let the agent read tickets and account notes automatically, but require approval before refunds, plan changes, or outbound messages.
CRM: allowBilling: askEmail: ask
Internal operations copilot
Give teammates a role that can inspect dashboards, search files, and draft fixes without handing it production shell access.
Files: allowTerminal: denySlack: allow
Partner-facing assistant
Expose a limited agent to customers or partners with scoped MCP tools and vault credentials for only their workspace.
MCP: scopedVault: scopedMemory: allow