The Zero Trust Access Controller takes a Jira elevated access request and evaluates it end-to-end. It reads the request and its justification, confirms whether a linked change record is approved or a linked incident is active and high severity, and checks the target asset’s state and CVE exposure in Lansweeper. It then recommends approve, approve conditionally, or deny — with specific, enforceable conditions where relevant — and, with the user’s confirmation, posts the evaluation as a comment on the ticket.
The agent is advisory only: it never grants, revokes or approves access itself, and every recommendation is designed to support the analyst’s decision, not replace it.

Lansweeper MCP
https://mcp.lansweeper.com/mcp
LLM
Claude 3.5+ — via Rovo (Atlassian’s agent platform runs on Claude models) and via the standalone Claude skill build
Atlassian Rovo, designed to work with any ITSM tool connected via MCP (Jira Service Management, ServiceNow, Freshservice)
Lansweeper plan
Starter, Pro, Enterprise
Claude skill — core justification and risk evaluation logic
standard instruction – site confirmation, query catalogue, active-asset filtering
This agent is available on two platforms: Atlassian Rovo and Claude. Steps 1 to 3 are the same shape everywhere; the platform-specific detail is called out where the steps diverge. Follow the column for your platform.
Step 1 — Download
Download the agent package from the location in section 6 below, or ask your Lansweeper contact for the current build.
Step 2 — Open your agent platform
Step 3 — Load the instructions
Step 4 — Connect Lansweeper
Authenticate the Lansweeper MCP connection (EU or US endpoint, as required) and confirm you can see your site list. Both platforms need this step; only the connection method in each platform’s settings differs.
Step 5 — Connect your ITSM tool
Connect the Jira MCP. Confirm the agent can read a test access request and its linked change or incident ticket before using it live.
Step 6 — First-run configuration (Claude skill only)
The Claude skill asks for five values on first use: your ITSM platform name, what your organisation calls access requests, change requests and incidents, and which connected MCP to use for your ITSM tool. The Rovo version has these values built into the instructions, so this step does not apply to it.
Step 7 — Run a test evaluation
Give the agent a test access request ticket key and ask for an evaluation. Confirm it assesses the justification before fetching any asset data, checks the linked ticket, and produces all five sections of the output format without fabricating CVE scores.