Drop a gap bullet from gaps.md by id. Idempotent:
AI agents call remove_gap to permanently remove resources in Ebony Enriching — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a gap record from persistent storage (gaps.md). Although the operation is idempotent (safe to retry), it destroys data without a reversible undo mechanism. In the context of a lab notebook system tracking research proposals and experiments, deleting gap signals cannot be undone and represents an irreversible modification of the research record.
From the tool's definition Tool description explicitly states 'Drop a gap bullet from `gaps.md` by id'. The verb 'drop' combined with removal of a record by identifier indicates irreversible deletion of data.
Attacks that exploit this kind of access
Drop a gap bullet from gaps.md by id. Idempotent:. It is categorised as a Destructive tool in the Ebony Enriching MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ebony Enriching MCP server in PolicyLayer and add a rule for remove_gap: 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 Ebony Enriching. Nothing to install.
remove_gap 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_gap 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_gap. 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_gap is provided by the Ebony Enriching MCP server (parkviewlab/ebony-enriching). 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 →