Secure Client Access Policies with Versa MCP Configuration Tool 

arun-chandar
By Arun Chandar
Lead Solution Architect
August 5, 2025
in
Share
Follow

This blog shows how bringing LLM-powered automation into policy management helps security and networking teams build, audit, and optimize network policies more efficiently. It integrates into existing workflows, offering real-time access to current configurations and intelligent policy insights — all without requiring teams to switch tools.

From MCP Server to SAC Policy Intelligence

Building on the foundation of the MCP Server, this blog demonstrates how it can be used to access, configure, and enforce secure access client policies more intelligently and effectively. The utility tackles a persistent operational challenge: fragmented policy management spread across dashboards, consoles, and chat interfaces. By centralizing policy visibility and applying LLM-powered analysis, it enables engineers to build, validate, and refine rules with greater speed and confidence. Key capabilities for managing Secure Access Client (SAC) rules include:

  • Detect duplicate or conflicting SAC rules to prevent policy sprawl.
  • Identifying misconfigurations, including failed device posture checks and security risks, using LLM-powered insights
  • Querying SAC rule configurations for user-level mappings, device posture checks, and operating system compatibility requirements.
  • Align policies with enterprise security standards using AI-driven validation.

Walkthrough

Let’s walk through a real-world scenario where the MCP Configuration Tool is used to create and delete a SAC rule. For this example, we will use Claude Desktop to interact with the MCP Server.

Step 1: Set Up the MCP Server

Note:

  • Modify the command field to match the Python location on your system. The example uses Python with uv.
  • Modify the run field to point to the correct .py file for the MCP server/tool on your local system (for STDIO mode) or follow the setup for SSE mode.
  • Replace the following environment variables with values from your infrastructure
    • DIRECTOR_URL
    • VN_USERNAME
    • VN_PASSWORD
    • VN_CLIENT_SECRET (generate this from the Director)
    • VN_CLIENT_ID (generate this from the Director)

Once complete, proceed to Step 2.

Step 2: Verify Claude is Connected to Versa MCP tools:

Next, launch Claude Desktop and confirm that it successfully connects to the MCP Server. Upon startup, the configuration panel displays all active integrations — including the Versa API Server if the connection is established.

From this panel, available tools can be reviewed and toggled on or off as needed.

Step 3: Create a SAC Rule for a Specific User

Next, we use Claude Desktop to define a new Secure Access Client (SAC) rule. In this case, the goal is to create a policy that applies specifically to Windows 10 devices used by a specific user.

Step 4: Verify the Rule in Versa Concerto

To confirm the rule was applied correctly, log into Versa Concerto and navigate to the SAC policy configuration page. There, we verify that the new rule — scoped to Windows 10 and the specific user — appears in the active policy list.

Step 5: Delete the SAC Rule

To remove the previously created SAC rule, we issue a prompt in Claude Desktop requesting its deletion.

Final Thoughts:

Recent Posts













Gartner Research Report

2024 Gartner® Magic QuadrantTM for SD-WAN

For the fifth year in a row, Versa has been positioned as a Leader in the Gartner Magic Quadrant for SD-WAN. We are one of only three recognized vendors to be in the Gartner Magic Quadrant reports for SD-WAN, Single-Vendor SASE, and Security Service Edge.