set_obfuscation · Mullvad MCP: Risk & Policy

WHAT IT DOES

What set_obfuscation does on Mullvad

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

WHY IT NEEDS A POLICY

Why set_obfuscation needs a policy

The 'set_' prefix clearly indicates this modifies configuration rather than merely reading it. Obfuscation settings affect VPN behavior but are reversible (can be changed back), making this Write rather than Destructive or Execute. No financial impact, no code execution, and no irreversible data loss.

From the tool's definition Tool name 'set_obfuscation' indicates modification of VPN obfuscation settings. The function name prefix 'set_' denotes a write/modify operation. Context from sibling tools (connect, disconnect, get_settings) confirms this is a settings management interface.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_obfuscation Rate-limited

set_obfuscation 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": {
    "set_obfuscation": {
      "limits": [
        {
          "counter": "set_obfuscation_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 Mullvad, so you can run agents against it safely.

FAQ

Questions about set_obfuscation

What does the set_obfuscation tool do? +

set_obfuscation. It is categorised as a Write tool in the Mullvad MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_obfuscation? +

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

What risk level is set_obfuscation? +

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

Can I rate-limit set_obfuscation? +

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

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

set_obfuscation is provided by the Mullvad MCP server (oresam-xyz/mullvad-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.