Clears the local cache of the Heim runtime which will attempt to stop the runtime and remove all applications, logs, metrics, etc. from the runtime.
AI agents call heim_clear to permanently remove resources in Heim MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs irreversible deletion of multiple categories of data (applications, logs, metrics) from the Heim runtime. While the scope is limited to the local runtime cache, the action cannot be undone and represents permanent loss of information. This makes it Destructive rather than Write (which would be reversible modification).
From the tool's definition Tool description states it will 'remove all applications, logs, metrics, etc. from the runtime' — this is irreversible deletion of data and runtime state.
Attacks that exploit this kind of access
Clears the local cache of the Heim runtime which will attempt to stop the runtime and remove all applications, logs, metrics, etc. from the runtime. It is categorised as a Destructive tool in the Heim MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Heim MCP server in PolicyLayer and add a rule for heim_clear: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Heim MCP. Nothing to install.
heim_clear is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the heim_clear rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for heim_clear. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
heim_clear is provided by the Heim MCP server (nor2-io/heim-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →