Get all custom field definitions for JIRA.
AI agents call jira_get_custom_fields to retrieve information from MCP JIRA Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about custom field definitions—a read-only operation with no capacity to modify, delete, execute code, or trigger external actions. The blast radius of misuse is minimal; an attacker gains only knowledge of available custom fields, not access to sensitive issue data or ability to alter system state. Confidence is high because the intent is unambiguous.
From the tool's definition Tool name 'jira_get_custom_fields' and description 'Get all custom field definitions for JIRA' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get all custom field definitions for JIRA. It is categorised as a Read tool in the MCP JIRA Server MCP Server, which means it retrieves data without modifying state.
Register the MCP JIRA Server MCP server in PolicyLayer and add a rule for jira_get_custom_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 MCP JIRA Server. Nothing to install.
jira_get_custom_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 jira_get_custom_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 jira_get_custom_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.
jira_get_custom_fields is provided by the MCP JIRA Server MCP server (tarangbhavsar/mcp-jira-server). 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 →