omg_delete_memory

Delete a project memory entry by key

SERVERGitlab Mcp SOURCE@zereight/mcp-gitlab

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-zereight-gitlab-mcp/omg-delete-memory.md

WHAT IT DOES

What omg_delete_memory does on Gitlab Mcp

AI agents call omg_delete_memory to permanently remove resources in Gitlab Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why omg_delete_memory is rated Critical

Deletion of data cannot be undone. While the blast radius is scoped to a single project memory entry (not entire projects or critical data), unauthorized deletion of project context or configuration could disrupt workflows. Classified as Destructive rather than Write because the operation is irreversible and permanent.

From the tool's definition Tool name includes 'delete' and description states 'Delete a project memory entry by key' — this is an irreversible deletion operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs omg_delete_memory safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Gitlab Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For omg_delete_memory, this is the rule to start with:

omg_delete_memory Hidden

omg_delete_memory is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "omg_delete_memory"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gitlab Mcp, apply this rule, and every omg_delete_memory call is checked against it from then on.

FAQ

Questions about omg_delete_memory

What does the omg_delete_memory tool do? +

Delete a project memory entry by key. It is categorised as a Destructive tool in the Gitlab Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on omg_delete_memory? +

Register the Gitlab MCP server in PolicyLayer and add a rule for omg_delete_memory: 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 Gitlab Mcp. Nothing to install.

What risk level is omg_delete_memory? +

omg_delete_memory is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit omg_delete_memory? +

Yes. Add a rate_limit block to the omg_delete_memory 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.

How do I block omg_delete_memory completely? +

Set action: deny in the PolicyLayer policy for omg_delete_memory. 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.

What MCP server provides omg_delete_memory? +

omg_delete_memory is provided by the Gitlab MCP server (@zereight/mcp-gitlab). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Gitlab, and thousands of servers like it.

This server

All 215 Gitlab tools → Critical-risk tools on this server →

Across the catalogue

delete_memory on Cognio →sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →