Elimina una instantánea por id.
AI agents call db_schema_delete to permanently remove resources in Schema Engram — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes database schema snapshots from the local SQLite file without the ability to undo the operation. Deletion is the defining characteristic of the Destructive category. While the blast radius is somewhat contained (only affects stored schema metadata, not production databases), the irreversible loss of structured data and potential disruption to LLM context memory justifies 'high' severity.
From the tool's definition Tool name 'db_schema_delete' and Spanish description 'Elimina una instantánea por id' (Deletes a snapshot by id) explicitly indicates irreversible deletion of stored data.
Attacks that exploit this kind of access
Elimina una instantánea por id. It is categorised as a Destructive tool in the Schema Engram MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Schema Engram MCP server in PolicyLayer and add a rule for db_schema_delete: 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 Schema Engram. Nothing to install.
db_schema_delete 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 db_schema_delete 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 db_schema_delete. 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.
db_schema_delete is provided by the Schema Engram MCP server (wabox32/schema-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 →