remove_server_configuration

Remove a server configuration from a client configuration

Server MCP Client Configuration Server landicefu/mcp-client-configuration-server
Category Destructive
Risk class Critical
Parameters 00 required

What remove_server_configuration does on MCP Client Configuration Server

AI agents call remove_server_configuration to permanently remove resources in MCP Client Configuration Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why remove_server_configuration needs a policy

This tool permanently deletes server configuration entries from client configuration files. Once removed, the configuration cannot be recovered without manual re-entry or backup restoration. This is a destructive operation affecting system state. While not as critical as removing all servers or corrupting core configs, it irreversibly modifies configuration state, qualifying it as Destructive rather than Write.

From the tool's definition Tool name is 'remove_server_configuration' with description 'Remove a server configuration from a client configuration'. The verb 'remove' paired with deletion of configuration entries is irreversible.

Questions about remove_server_configuration

What does the remove_server_configuration tool do? +

Remove a server configuration from a client configuration. It is categorised as a Destructive tool in the MCP Client Configuration Server 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 remove_server_configuration? +

Register the MCP Client Configuration Server MCP server in PolicyLayer and add a rule for remove_server_configuration: 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 Client Configuration Server. Nothing to install.

What risk level is remove_server_configuration? +

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

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

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

remove_server_configuration is provided by the MCP Client Configuration Server MCP server (landicefu/mcp-client-configuration-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

remove_server_configuration is one line of MCP Client Configuration Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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.