AI agents call get_ticket_fields to retrieve information from Jira without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves field definitions and metadata from Jira—a purely informational operation with no side effects. It does not create, modify, delete, or execute operations. The purpose is to help users understand available fields, which is a classic Read category operation with minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'get_ticket_fields' and description 'Get all available fields and their metadata for a Jira ticket' indicate a query operation that retrieves metadata without modifying data.
Attacks that exploit this kind of access
Get all available fields and their metadata for a Jira ticket (useful for finding custom field IDs). It is categorised as a Read tool in the Jira MCP Server, which means it retrieves data without modifying state.
Register the Jira MCP server in PolicyLayer and add a rule for get_ticket_fields: 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. Nothing to install.
get_ticket_fields 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_ticket_fields 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_ticket_fields. 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_ticket_fields is provided by the Jira MCP server (taraskhust/jira-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_ticket_fields is one line of Jira's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →