Retrieves available priorities (e.g., Highest, High, Medium, Low, Lowest). Returns IDs, names, and descriptions.
AI agents call jira_get_priorities to retrieve information from Mcp Jira Stdio without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves static configuration data about available priorities in Jira. It performs no create, update, delete, or execute operations. The data returned is reference information used for understanding system options, not sensitive user data. Misuse would have minimal blast radius—an agent could only read priority metadata that is typically non-sensitive and widely available to Jira users.
From the tool's definition Tool name 'jira_get_priorities' and description 'Retrieves available priorities' indicate a query operation that returns reference data (priority IDs, names, descriptions) with no data modification or side effects.
Attacks that exploit this kind of access
Retrieves available priorities (e.g., Highest, High, Medium, Low, Lowest). Returns IDs, names, and descriptions. It is categorised as a Read tool in the Mcp Jira Stdio MCP Server, which means it retrieves data without modifying state.
Register the Mcp Jira Stdio 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 Mcp Jira Stdio. 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 Mcp Jira Stdio MCP server (mcp-jira-stdio). 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 →