add_server_configuration

WHAT IT DOES

What add_server_configuration does on MCP Client Configuration Server

AI agents use add_server_configuration to create or update resources in MCP Client Configuration Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Client Configuration Server environment.

WHY IT NEEDS A POLICY

Why add_server_configuration needs a policy

This tool creates or modifies configuration files that control how AI assistants connect to and interact with MCP servers. While reversible (configurations can be updated or removed), it has high severity because malicious configurations could redirect AI assistants to compromised servers, inject arbitrary MCP server endpoints, or alter client behavior in ways that affect all downstream AI operations.

From the tool's definition Tool name 'add_server_configuration' and description 'Add or update a server configuration in a client configuration' explicitly indicate creation and modification of configuration data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_server_configuration Rate-limited

add_server_configuration stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_server_configuration": {
      "limits": [
        {
          "counter": "add_server_configuration_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Client Configuration Server, so you can run agents against it safely.

FAQ

Questions about add_server_configuration

What does the add_server_configuration tool do? +

Add or update a server configuration in a client configuration. It is categorised as a Write tool in the MCP Client Configuration Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_server_configuration? +

Register the MCP Client Configuration Server MCP server in PolicyLayer and add a rule for add_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 add_server_configuration? +

add_server_configuration is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_server_configuration? +

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

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

add_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.