get_all_projects
AI agents call get_all_projects to retrieve information from MCP Atlassian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves project data from Atlassian Cloud without modifying, deleting, or executing operations. The blast radius of misuse is minimal—an agent could enumerate projects but cannot alter system state or access sensitive data beyond project metadata. Low severity reflects the read-only nature and typical non-sensitive scope of project listings.
From the tool's definition Tool name 'get_all_projects' indicates a retrieval operation. The verb 'get' and absence of modification language confirm read-only semantics.
Attacks that exploit this kind of access
get_all_projects. It is categorised as a Read tool in the MCP Atlassian MCP Server, which means it retrieves data without modifying state.
Register the MCP Atlassian MCP server in PolicyLayer and add a rule for get_all_projects: 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 MCP Atlassian. Nothing to install.
get_all_projects 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 get_all_projects 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 get_all_projects. 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.
get_all_projects is provided by the MCP Atlassian MCP server (sooperset/mcp-atlassian). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.