Discover all custom field IDs and names in QuickText Jira. Useful for understanding field mapping (customfield_10023 = Story point estimate, etc.). Example: quinta-jira_get_custom_fields({})
AI agents call quinta-jira_get_custom_fields 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 retrieves and lists custom field metadata from Jira without modifying, deleting, or executing any operations. It has no side effects and serves only to provide information about field structure for mapping purposes. The blast radius of misuse is minimal—an agent could only learn about field names and IDs, which is non-sensitive metadata already accessible to Jira users with basic permissions.
From the tool's definition Tool name contains 'get_' prefix and description states it 'Discover all custom field IDs and names' - a query operation that retrieves metadata about field configuration. The empty parameter example {} indicates no data modification occurs.
Attacks that exploit this kind of access
Discover all custom field IDs and names in QuickText Jira. Useful for understanding field mapping (customfield_10023 = Story point estimate, etc.). Example: quinta-jira_get_custom_fields({}). 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 quinta-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 JIRA MCP Server. Nothing to install.
quinta-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 quinta-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 quinta-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.
quinta-jira_get_custom_fields is provided by the JIRA MCP Server MCP server (jasseramri/jira-mcp-quicktext). 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 →