AI agents call get_device_info to retrieve information from Mullvad without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a Read operation—it retrieves account-associated device data without altering it. The severity is medium rather than low because device information is sensitive and could be leveraged by a malicious agent for reconnaissance, lateral movement, or device targeting, though it doesn't directly compromise the VPN connection or enable financial harm.
From the tool's definition Tool name 'get_device_info' and description 'Get information about devices registered to the Mullvad account' indicate data retrieval with no modifications.
Attacks that exploit this kind of access
Get information about devices registered to the Mullvad account. It is categorised as a Read tool in the Mullvad MCP Server, which means it retrieves data without modifying state.
Register the Mullvad MCP server in PolicyLayer and add a rule for get_device_info: 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.
get_device_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_device_info 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 get_device_info. 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.
get_device_info 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.
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 →