MCPサーバー設定を削除する。
AI agents call remove_server to permanently remove resources in MCP Configuration Editor — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes MCP server configurations. Once deleted, the configuration cannot be recovered without manual restoration from backups. This is a destructive operation that eliminates data and could disrupt critical integrations if misused by an AI agent. Although the parent service mentions 'automatic backups', the removal itself is irreversible at the tool level.
From the tool's definition Tool name 'remove_server' combined with description indicating deletion of MCP server configuration. The Japanese description 'MCPサーバー設定を削除する' translates to 'Delete/Remove MCP server configuration', which is an irreversible operation.
Attacks that exploit this kind of access
MCPサーバー設定を削除する。. It is categorised as a Destructive tool in the MCP Configuration Editor MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Configuration Editor MCP server in PolicyLayer and add a rule for remove_server: 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 MCP Configuration Editor. Nothing to install.
remove_server 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_server 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_server. 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_server is provided by the MCP Configuration Editor MCP server (r3-yamauchi/mcp-conf-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 →