指定した名前の接続プロファイルを削除します
AI agents call remove_profile to permanently remove resources in MySQL MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes stored database connection profiles. While not directly accessing data, deletion of configuration profiles is irreversible and could disrupt database access, authentication workflows, or expose systems if profiles are restored improperly. This qualifies as Destructive rather than Write because the action cannot be undone without manual restoration.
From the tool's definition Tool name is 'remove_profile' and description states '指定した名前の接続プロファイルを削除します' (removes/deletes the connection profile with the specified name). The verb '削除' explicitly means 'delete' or 'remove', indicating irreversible deletion.
Attacks that exploit this kind of access
指定した名前の接続プロファイルを削除します. It is categorised as a Destructive tool in the MySQL MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MySQL MCP Server MCP server in PolicyLayer and add a rule for remove_profile: 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 Server. Nothing to install.
remove_profile is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_profile 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.
Set action: deny in the PolicyLayer policy for remove_profile. 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.
remove_profile is provided by the MySQL MCP Server MCP server (yuki777/mysql-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →