configs_update_settings

Server StealthSurf MCP Server stealthsurf-vpn/mcp

Category Write

Risk class Medium

Parameters 00 required

WHAT IT DOES

What configs_update_settings does on StealthSurf MCP Server

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

WHY IT NEEDS A POLICY

Why configs_update_settings needs a policy

An AI agent can call configs_update_settings faster than any human can review — one bad instruction and it creates or modifies resources in StealthSurf MCP Server by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

configs_update_settings Rate-limited

configs_update_settings 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": {
    "configs_update_settings": {
      "limits": [
        {
          "counter": "configs_update_settings_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 StealthSurf MCP Server, so you can run agents against it safely.

FAQ

Questions about configs_update_settings

What does the configs_update_settings tool do? +

Update VPN config settings: change protocol, location, server, and extended options. Location and protocol are required. Server is auto-selected if omitted. Extended settings (WARP, Reality, transport, etc.) only apply when use_extended_settings=true. Changing protocol or location may regenerate the connection_url. It is categorised as a Write tool in the StealthSurf MCP 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 configs_update_settings? +

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

What risk level is configs_update_settings? +

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

Can I rate-limit configs_update_settings? +

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

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

configs_update_settings is provided by the StealthSurf MCP Server MCP server (stealthsurf-vpn/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.