remove_entity_links

THE RISK

Critical Risk

Why remove_entity_links needs a policy

The tool removes existing relationships/links between sources and entities. Removing links is typically an irreversible destructive action — once the associations are deleted, the relational data is lost unless manually recreated. No indication of soft-delete or undo functionality.

From the tool's definition Remove links between sources and entities

Documented attack patterns abuse exactly the kind of access remove_entity_links gives an agent:

POLICY

How to control remove_entity_links

PolicyLayer is an MCP gateway — it sits between your AI agents and literateMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_entity_links:

policy.json

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

remove_entity_links disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register literateMCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More literateMCP tools

Execute vacuum_database Optimize the database by running VACUUM. Write link_to_entities Link multiple sources to entities. Write add_identifiers Add new identifiers to multiple sources in a single transaction. Write add_notes Add notes to multiple sources in a single transaction. Write add_sources Add multiple new sources with duplicate checking. Write update_entity_links Update existing links between sources and entities. Write update_status Update status for multiple sources in a single transaction. Read describe_table Describe a table schema.

All 15 literateMCP tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in literateMCP → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about remove_entity_links

What does the remove_entity_links tool do? +

Remove links between sources and entities. It is categorised as a Destructive tool in the literateMCP 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_entity_links? +

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

What risk level is remove_entity_links? +

remove_entity_links 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_entity_links? +

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

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

remove_entity_links is provided by the literate MCP server (zongmin-yu/sqlite-literature-management-fastmcp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every literateMCP tool call.

Start from literateMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →