AI agents call jira_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.
The 'get_' prefix and project retrieval semantics align with Read operations—querying and listing data with no side effects. Although the description is empty (lowering confidence slightly), the tool name and its position among other Jira query tools (get_jira_issue) provide sufficient evidence. No capability to create, execute code, delete, or move money is indicated.
From the tool's definition Tool name 'jira_get_all_projects' indicates a retrieval operation following the 'get_' prefix pattern. No description provided, but the naming convention and context among sibling tools (which include get_* and create_*/update_* operations) strongly suggests…
Documented attack patterns abuse exactly the kind of access jira_get_all_projects gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Atlassian, and nothing reaches the server without passing your rules. This is the rule we recommend for jira_get_all_projects:
{
"version": "1",
"default": "deny",
"tools": {
"jira_get_all_projects": {}
}
}jira_get_all_projects is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
jira_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 jira_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.
jira_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 jira_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 jira_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.
jira_get_all_projects is provided by the MCP Atlassian MCP server (samwang0723/mcp-atlassian). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Atlassian, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 MCP Atlassian tools catalogued and risk-classified — across an index of 43,000+ MCP servers.