shared-memory-delete

Delete a shared memory item. Only the owner can delete the item.

Server MCP LLM Generator v2 mako10k/mcp-llm-generator
Category Destructive
Risk class Critical
Parameters 00 required

What shared-memory-delete does on MCP LLM Generator v2

AI agents call shared-memory-delete to permanently remove resources in MCP LLM Generator v2 — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why shared-memory-delete needs a policy

This tool permanently removes data (shared memory items) and cannot be undone. Deletion is irreversible, which places it in the Destructive category rather than Write. The severity is high because an AI agent with misuse could delete important shared memory/context data relied upon by other users or systems, though the access control ('Only the owner can delete') provides some mitigation.

From the tool's definition Tool name contains 'delete' and description states 'Delete a shared memory item.' The action is irreversible data removal.

Questions about shared-memory-delete

What does the shared-memory-delete tool do? +

Delete a shared memory item. Only the owner can delete the item. It is categorised as a Destructive tool in the MCP LLM Generator v2 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 shared-memory-delete? +

Register the MCP LLM Generator v2 MCP server in PolicyLayer and add a rule for shared-memory-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 MCP LLM Generator v2. Nothing to install.

What risk level is shared-memory-delete? +

shared-memory-delete 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 shared-memory-delete? +

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

How do I block shared-memory-delete completely? +

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

What MCP server provides shared-memory-delete? +

shared-memory-delete is provided by the MCP LLM Generator v2 MCP server (mako10k/mcp-llm-generator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

shared-memory-delete is one line of MCP LLM Generator v2's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.