List Jira projects accessible to the account
AI agents call getVisibleJiraProjects to retrieve information from Atlassian Multi without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that lists projects the user has access to. It has no side effects, does not create, modify, or delete data, and does not execute arbitrary code or commit financial resources. The blast radius is minimal—an AI agent using this tool can only discover what projects exist in the workspace, which is typically non-sensitive discovery information.
From the tool's definition Tool name 'getVisibleJiraProjects' and description 'List Jira projects accessible to the account' indicate a query/list operation that retrieves data without modifying it.
Attacks that exploit this kind of access
List Jira projects accessible to the account. It is categorised as a Read tool in the Atlassian Multi MCP Server, which means it retrieves data without modifying state.
Register the Atlassian Multi MCP server in PolicyLayer and add a rule for getVisibleJiraProjects: 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 Atlassian Multi. Nothing to install.
getVisibleJiraProjects is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getVisibleJiraProjects 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 getVisibleJiraProjects. 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.
getVisibleJiraProjects is provided by the Atlassian Multi MCP server (ntlongctt/atlassian-multi-mcp). 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 →