Remove a model from the current session.
AI agents call remove_model to permanently remove resources in Orionbelt Semantic Layer — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a model from a session destroys or deletes that model definition, which is an irreversible action that cannot be undone without re-importing or recreating the model. This aligns with the Destructive category (delete, drop, purge). While the impact is scoped to the current session, the loss of the model definition and any associated metadata qualifies as a destructive operation.
From the tool's definition Tool is named 'remove_model' and described as 'Remove a model from the current session.' The verb 'remove' in the context of model management indicates deletion or destruction of a semantic model.
Attacks that exploit this kind of access
Remove a model from the current session. It is categorised as a Destructive tool in the Orionbelt Semantic Layer MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Orionbelt Semantic Layer MCP server in PolicyLayer and add a rule for remove_model: 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 Orionbelt Semantic Layer. Nothing to install.
remove_model 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 remove_model 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 remove_model. 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.
remove_model is provided by the Orionbelt Semantic Layer MCP server (ralfbecher/orionbelt-semantic-layer-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 →