AI agents call get_multiple_projects_tool to retrieve information from MCP Jira without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves project information from Jira without modifying any data. It follows the naming pattern of other Read operations on the server (get_* prefix). Even though the description is empty, the tool name and context of sibling tools provide sufficient evidence that this performs a query/fetch operation with no side effects or destructive capability.
From the tool's definition Tool name 'get_multiple_projects_tool' indicates retrieval of project data. Sibling tools (get_issue_tool, get_project_by_id_tool, get_project_by_key_tool) establish a Read pattern for GET operations on this Jira server.
Attacks that exploit this kind of access
get_multiple_projects_tool. It is categorised as a Read tool in the MCP Jira MCP Server, which means it retrieves data without modifying state.
Register the MCP Jira MCP server in PolicyLayer and add a rule for get_multiple_projects_tool: 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 Jira. Nothing to install.
get_multiple_projects_tool 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_multiple_projects_tool 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_multiple_projects_tool. 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_multiple_projects_tool is provided by the MCP Jira MCP server (tusharshahi/mcp-jira). 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 →