Update Remote Access VPN settings
AI agents use update_remote_access_vpn to create or update resources in CloudStack MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CloudStack MCP Server environment.
The tool modifies VPN settings reversibly (configuration can be changed again), placing it in the Write category. Severity is high because misconfiguration of remote access VPN settings could expose infrastructure to unauthorized access or network vulnerabilities, affecting security controls.
From the tool's definition Tool description states 'Update Remote Access VPN settings' - the word 'Update' indicates modification of existing configuration. This is VPN infrastructure configuration which affects network security posture.
Attacks that exploit this kind of access
Update Remote Access VPN settings. It is categorised as a Write tool in the CloudStack MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for update_remote_access_vpn: 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 CloudStack MCP Server. Nothing to install.
update_remote_access_vpn 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 update_remote_access_vpn 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 update_remote_access_vpn. 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.
update_remote_access_vpn is provided by the CloudStack MCP Server MCP server (mozg31337/cloudstack-mcp-server). 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 →