Block or unblock a specific device. Blocked devices cannot use VPN until unblocked. Useful for revoking access from lost/stolen devices.
AI agents use devices_set_blocked 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 devices_set_blocked 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
Block or unblock a specific device. Blocked devices cannot use VPN until unblocked. Useful for revoking access from lost/stolen devices. 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 devices_set_blocked: 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.
devices_set_blocked 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 devices_set_blocked 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 devices_set_blocked. 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.
devices_set_blocked 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.