paid_options_update_limits · StealthSurf MCP Server MCP

WHAT IT DOES

What paid_options_update_limits does on StealthSurf MCP Server

AI agents use paid_options_update_limits 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 paid_options_update_limits needs a policy

An AI agent can call paid_options_update_limits 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

paid_options_update_limits Rate-limited

paid_options_update_limits 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": {
    "paid_options_update_limits": {
      "limits": [
        {
          "counter": "paid_options_update_limits_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 paid_options_update_limits

What does the paid_options_update_limits tool do? +

Update device and traffic limits for a paid option. Controls how many devices can connect simultaneously and optional traffic cap. 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 paid_options_update_limits? +

Register the StealthSurf MCP Server MCP server in PolicyLayer and add a rule for paid_options_update_limits: 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 paid_options_update_limits? +

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

Can I rate-limit paid_options_update_limits? +

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

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

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