reconnect

reconnect

Server Mullvad oresam-xyz/mullvad-mcp
Category Execute
Risk class High
Parameters 00 required

What reconnect does on Mullvad

AI agents invoke reconnect to trigger actions in Mullvad. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

Why reconnect needs a policy

Based on the tool name and server context (Mullvad VPN controller), 'reconnect' most likely disconnects and reconnects the VPN, triggering an external network operation. This is an Execute-category action as it affects the VPN connection state. Confidence is reduced due to the empty description.

From the tool's definition Tool name is 'reconnect'; description is empty or uninformative.

Questions about reconnect

What does the reconnect tool do? +

reconnect. It is categorised as a Execute tool in the Mullvad MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on reconnect? +

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

reconnect is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit reconnect? +

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

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

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

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.