AI agents call jira_get_field_options to retrieve information from Jiraxmcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries Jira's custom field configuration to retrieve allowed options for a field in a specific context. It is a read-only operation that returns configuration data with no side effects, no code execution, and no data modification or deletion. The low severity reflects that field option metadata is typically non-sensitive and misconfiguration causes no irreversible harm.
From the tool's definition Tool name contains 'get' and description states 'Get allowed options' — retrieves field metadata without modifying or executing operations.
Attacks that exploit this kind of access
Get allowed options for a Jira custom field context. It is categorised as a Read tool in the Jiraxmcp MCP Server, which means it retrieves data without modifying state.
Register the Jirax 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 Jiraxmcp. 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 Jirax MCP server (vaibhavpandeyvpz/jiraxmcp). 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 →