empty_trash

Permanently delete all trashed records and their dependent indexes.

Server Scifinder Route kettly1260/scifinder-route-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What empty_trash does on Scifinder Route

AI agents call empty_trash to permanently remove resources in Scifinder Route — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why empty_trash needs a policy

This tool performs permanent deletion of data that cannot be undone. It is classified as Destructive rather than Execute because the operation is inherently destructive in nature—it irreversibly removes data. The high severity reflects that a misused agent could lose entire synthetic route databases and their supporting indexes, which would be difficult or impossible to recover.

From the tool's definition Tool description explicitly states 'Permanently delete all trashed records and their dependent indexes.' The word 'permanently' combined with 'delete' and the scope of deletion (records and dependent indexes) clearly indicates irreversible data loss.

Questions about empty_trash

What does the empty_trash tool do? +

Permanently delete all trashed records and their dependent indexes. It is categorised as a Destructive tool in the Scifinder Route 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 empty_trash? +

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

What risk level is empty_trash? +

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

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

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

empty_trash is provided by the Scifinder Route MCP server (kettly1260/scifinder-route-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

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.