Default-deny for the unknown
A tool that has not been registered and approved is not trusted. If policy does not explicitly allow the action, HELM denies it.
MCP quarantine
HELM treats unregistered MCP tools and external tool output as untrusted. When an agent reaches for an unknown tool, the action is denied by default and a quarantine receipt is preserved.
Unknown means untrusted. Untrusted means denied. Denied means recorded.
The default
When an agent can reach arbitrary MCP tools, every unknown tool carries its own blast radius. HELM closes that gap by treating the unknown as untrusted and denying its action until someone approves it.
A tool that has not been registered and approved is not trusted. If policy does not explicitly allow the action, HELM denies it.
HELM treats external tool output and MCP servers as untrusted unless explicitly normalized and approved, so unreviewed output cannot act on your behalf.
A quarantined tool call is not silent. The denial is bound to the policy that produced it and preserved as a receipt.
One path, walked through
Agent proposes
Agent invokes an unregistered MCP tool
HELM checks policy
Quarantines the unknown tool and checks the action
Verdict
DENY
Proof
Quarantine receipt + EvidencePack
Quarantine lifecycle
Quarantine is not a dead end. It is a default-deny holding state with a clear path to approval.
Step 1
An agent reaches for an MCP tool that is not registered or not approved.
Step 2
HELM quarantines the unknown tool and checks the proposed action against policy.
Step 3
With no explicit allowance, the action is denied. Nothing runs.
Step 4
The denial and its policy are recorded as a quarantine receipt and EvidencePack.
Step 5
A reviewer can register and scope the tool. Only then does the action become eligible to run.
The deny receipt
A blocked call that leaves no trace teaches you nothing. HELM preserves the denial so the attempt, the policy, and the source are all auditable later.
The proposed side effect and the tool that asked for it.
The policy that produced the deny, bound to the verdict.
The quarantine receipt and EvidencePack verify outside any dashboard.
Questions
It means an unregistered or unapproved MCP tool is treated as untrusted on contact. HELM quarantines the unknown tool, checks the proposed action against policy, and denies it by default. Nothing runs until the tool is explicitly registered and scoped.
A tool you have not reviewed can cause a side effect you did not intend. Denying by default means an unapproved action stops rather than proceeds, and the attempt is preserved as evidence instead of passing through unseen.
Yes. HELM treats external tool output and MCP servers as untrusted unless explicitly normalized and approved. Output from a quarantined source does not get to act on your behalf.
A quarantine receipt and EvidencePack record the denied action, the policy that denied it, and the source. Both verify offline, so the attempt is auditable later by anyone.
Keep reading
Terms
A small bundle of records used to verify one event or review path.
Use for replayable evidence slices.A record chain that helps replay and check what happened.
Use for HELM proof records and replay paths.HELM lets the action run.
Use as a canonical verdict.HELM blocks the action.
Use as a canonical verdict.HELM stops and asks for more facts, policy, or human approval.
Use as the canonical non-dispatch path for missing facts, policy hold, or approval.Bring one unregistered tool to the boundary and watch the default-deny verdict and its receipt.