remove_project_glossary_term

v2.1.0 \u2014 Remove a glossary entry by term. Returns true if found.

SERVEREnhanced Knowledge Graph Memory Server SOURCEdanielsimonjr/memory-mcp
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/danielsimonjr-memory-mcp/remove-project-glossary-term.md

What remove_project_glossary_term does on Enhanced Knowledge Graph Memory Server

AI agents call remove_project_glossary_term to permanently remove resources in Enhanced Knowledge Graph Memory Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why remove_project_glossary_term is rated Critical

An AI agent that decides to call remove_project_glossary_term doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Enhanced Knowledge Graph Memory Server is gone. There is no undo for destructive operations.

Questions about remove_project_glossary_term

What does the remove_project_glossary_term tool do? +

v2.1.0 \u2014 Remove a glossary entry by term. Returns true if found. It is categorised as a Destructive tool in the Enhanced Knowledge Graph Memory Server 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 remove_project_glossary_term? +

Register the Enhanced Knowledge Graph Memory Server MCP server in PolicyLayer and add a rule for remove_project_glossary_term: 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 Enhanced Knowledge Graph Memory Server. Nothing to install.

What risk level is remove_project_glossary_term? +

remove_project_glossary_term 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 remove_project_glossary_term? +

Yes. Add a rate_limit block to the remove_project_glossary_term 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 remove_project_glossary_term completely? +

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

remove_project_glossary_term is provided by the Enhanced Knowledge Graph Memory Server MCP server (danielsimonjr/memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Enhanced Knowledge Graph Memory Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Enhanced Knowledge Graph Memory Server's. Pull the full record:

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.