Critical Risk →

remove_term

Remove a term from the organizational glossary by its ID. This permanently deletes the term and its code location mappings. Returns the deleted term's details for confirmation.

Single-target operation

Part of the Lingo MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents may call remove_term to permanently remove or destroy resources in Lingo. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call remove_term in a loop, permanently destroying resources in Lingo. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

lingo.yaml
tools:
  remove_term:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Lingo policy for all 13 tools.

Tool Name remove_term
Category Destructive
MCP Server Lingo MCP Server
Risk Level Critical

View all 13 tools →

Agents calling destructive-class tools like remove_term have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

remove_term is one of the critical-risk operations in Lingo. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the remove_term tool do? +

Remove a term from the organizational glossary by its ID. This permanently deletes the term and its code location mappings. Returns the deleted term's details for confirmation.. It is categorised as a Destructive tool in the Lingo 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_term? +

Add a rule in your Intercept YAML policy under the tools section for remove_term. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Lingo MCP server.

What risk level is remove_term? +

remove_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_term? +

Yes. Add a rate_limit block to the remove_term rule in your Intercept 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_term completely? +

Set action: deny in the Intercept policy for remove_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_term? +

remove_term is provided by the Lingo MCP server (@hyukyyy/lingo-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.