Change the protocol of an existing subconfig (HTTP ↔ SOCKS5). Regenerates the connection_url for the new protocol.
AI agents use configs_update_subconfig 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.
An AI agent can call configs_update_subconfig 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
Change the protocol of an existing subconfig (HTTP ↔ SOCKS5). Regenerates the connection_url for the new protocol. 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.
Register the StealthSurf MCP Server MCP server in PolicyLayer and add a rule for configs_update_subconfig: 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.
configs_update_subconfig is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the configs_update_subconfig 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 configs_update_subconfig. 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.
configs_update_subconfig 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.