delete_knowledge_database

A destructive tool on the Metis Public Health MCP server.

SERVERMetis Public Health SOURCEsveritg/metis_ph

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/sveritg-metis-ph/delete-knowledge-database.md

WHAT IT DOES

What delete_knowledge_database does on Metis Public Health

AI agents call delete_knowledge_database to permanently remove resources in Metis Public Health, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why delete_knowledge_database is rated Critical

Irreversibly deletes user's indexed PDF library and knowledge data; no undo possible.

From the tool's definition delete_knowledge_database with empty description; destroys indexed knowledge irreversibly.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_knowledge_database safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Metis Public Health, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_knowledge_database, this is the rule to start with:

delete_knowledge_database Hidden

delete_knowledge_database is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Metis Public Health, apply this rule, and every delete_knowledge_database call is checked against it from then on.

FAQ

Questions about delete_knowledge_database

What does the delete_knowledge_database tool do? +

delete_knowledge_database is a destructive tool on the Metis Public Health MCP server. It is categorised as a Destructive tool in the Metis Public Health 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 delete_knowledge_database? +

Register the Metis Public Health MCP server in PolicyLayer and add a rule for delete_knowledge_database: 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 Metis Public Health. Nothing to install.

What risk level is delete_knowledge_database? +

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

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

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

delete_knowledge_database is provided by the Metis Public Health MCP server (sveritg/metis_ph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Metis Public Health, and thousands of servers like it.

This server

All 277 Metis Public Health tools → Critical-risk tools on this server →

Across the catalogue

delete_mysql_database on cPanel MCP Server →sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →