mysql_fulltext_drop

Drop a FULLTEXT index from a table.

SERVERMysql Mcp SOURCEoci:docker.io/writenotenow/mysql-mcp:v1.0.0

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/io-github-neverinfamous-mysql-mcp/mysql-fulltext-drop.md

WHAT IT DOES

What mysql_fulltext_drop does on Mysql Mcp

AI agents call mysql_fulltext_drop to permanently remove resources in Mysql Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why mysql_fulltext_drop is rated Critical

This tool removes a FULLTEXT index, which is an irreversible destructive action. While not as severe as dropping an entire table, deleting indexes can impact query performance and cannot be undone without recreation. Classified as Destructive rather than Write because DROP operations are inherently irreversible data structure modifications.

From the tool's definition Tool name includes 'drop' and description states 'Drop a FULLTEXT index from a table.' DROP operations irreversibly remove database objects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mysql_fulltext_drop safely

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

mysql_fulltext_drop Hidden

mysql_fulltext_drop 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": [
    "mysql_fulltext_drop"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mysql Mcp, apply this rule, and every mysql_fulltext_drop call is checked against it from then on.

FAQ

Questions about mysql_fulltext_drop

What does the mysql_fulltext_drop tool do? +

Drop a FULLTEXT index from a table. It is categorised as a Destructive tool in the Mysql Mcp 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 mysql_fulltext_drop? +

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

What risk level is mysql_fulltext_drop? +

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

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

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

mysql_fulltext_drop is provided by the Mysql MCP server (oci:docker.io/writenotenow/mysql-mcp:v1.0.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mysql, and thousands of servers like it.

This server

All 223 Mysql tools → Critical-risk tools on this server →

Across the catalogue

delete_mysql_database on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →