Get allowed values/options for a specific field in a project and issue type context
AI agents call jira_get_field_options 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 queries field options/constraints for a given project and issue type context. It has no side effects, does not execute code, does not modify data, and does not delete or move resources. The action is purely informational retrieval of allowed field values, which is a read operation with minimal blast radius if misused by an agent.
From the tool's definition Tool name contains 'get' and description states 'Get allowed values/options for a specific field' — this retrieves configuration/metadata without modifying data.
Attacks that exploit this kind of access
Get allowed values/options for a specific field in a project and issue type context. 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_field_options: 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_field_options 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_field_options 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_field_options. 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_field_options 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 →