Create a VPN config for a paid option. The config is bound to the paid option
AI agents use paid_option_configs_create 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 paid_option_configs_create 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
Create a VPN config for a paid option. The config is bound to the paid option. 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 paid_option_configs_create: 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.
paid_option_configs_create 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 paid_option_configs_create 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 paid_option_configs_create. 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.
paid_option_configs_create 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.