Get all available priorities
AI agents call jira_get_priorities to retrieve information from Jira MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple data retrieval operation to fetch the list of available priorities in Jira. It has no side effects, creates no data, modifies nothing, and cannot be misused to cause harm. The blast radius of misuse is minimal—an agent could only learn what priorities exist in the system. This is a straightforward Read category tool.
From the tool's definition Tool name 'jira_get_priorities' and description 'Get all available priorities' indicate a read-only retrieval operation that queries and returns existing priority data without modification, creation, or deletion.
Attacks that exploit this kind of access
Get all available priorities. It is categorised as a Read tool in the Jira MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Jira MCP Server MCP server in PolicyLayer and add a rule for jira_get_priorities: 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 Jira MCP Server. Nothing to install.
jira_get_priorities 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_priorities 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_priorities. 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_priorities is provided by the Jira MCP Server MCP server (yogeshhrathod/jiramcp). 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 →