Known limitations

Last updated 2026-10-05

We state these plainly so you can plan.

AgentLens governs agents that connect through it. Agents using Atlassian's own MCP server or REST API tokens are visible in the Monitor but not blocked. The getting-started guide (step 7) shows how to close those routes in Atlassian Administration.
The MCP capability is in Preview. The tools come from Atlassian's Forge "rovo:mcp" capability, which Atlassian marks as Preview, with external AI clients in early access. Atlassian may change it.
One-time switches and approvals. A site admin must click "Enable tools" for the app once (Atlassian Administration, Connected apps), and each person approves the connection once in their AI client and once for AgentLens.
Rules cannot target an AI client. The app cannot tell which AI client made a call (Atlassian does not pass it), so rules work per person, group and project, not per client.
Approved changes show the app as author. They are applied by the app on the requester's behalf, so the author shown in Jira is "AgentLens for Jira", with the requester and approver named in comments and in the audit log.
No attachments, no Confluence yet. Attachments are not read or written in this version; Confluence is not covered yet.
Not on the Atlassian Marketplace yet. AgentLens is coming soon; until the listing is live it cannot be installed.

Was this page helpful? Email support@mortiseapps.com.