This record as markdown: /tools/cbrown35-20i-mcp/lock-vps-vnc.md
What lock_vps_vnc does on 20i MCP Server
AI agents use lock_vps_vnc to create or update resources in 20i MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 20i MCP Server environment.
Why lock_vps_vnc is rated Medium
Locking VNC console access is a reversible write/configuration action that restricts access to a VPS console. It modifies a security setting but does not delete data or execute code. It can presumably be unlocked, making it reversible. Misuse could lock out legitimate administrators from emergency console access, hence medium severity.
From the tool's definition Lock VNC console access
Attacks that exploit this kind of access
The rule that runs lock_vps_vnc safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 20i MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For lock_vps_vnc, this is the rule to start with:
lock_vps_vnc 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.
The button opens the PolicyLayer dashboard: create your workspace, connect 20i MCP Server, apply this rule, and every lock_vps_vnc call is checked against it from then on.
Questions about lock_vps_vnc
Lock VNC console access. It is categorised as a Write tool in the 20i MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 20i MCP Server MCP server in PolicyLayer and add a rule for lock_vps_vnc: 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 20i MCP Server. Nothing to install.
lock_vps_vnc 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 lock_vps_vnc 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 lock_vps_vnc. 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.
lock_vps_vnc is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 20i MCP Server, and thousands of servers like it.
This server
Across the catalogue