Retrieves all custom fields available in Jira. Shows custom field names, IDs (e.g., customfield_10071), and types. Useful for discovering what custom fields exist and their identifiers.
AI agents call jira_get_custom_fields to retrieve information from Mcp Jira Stdio without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
projectKey | string | — | Project key to filter custom fields (optional) |
Parameters from the server's own tool schema.
This tool retrieves metadata about custom fields in Jira without modifying, deleting, or executing any operations. It is purely informational, similar to discovery/introspection operations. The action 'retrieves' and the passive nature of the operation (showing names, IDs, and types) confirms this is a Read category tool. Severity is low because disclosure of field metadata poses minimal security risk.
From the tool's definition Tool name 'jira_get_custom_fields' and description 'Retrieves all custom fields available in Jira' indicates a query operation with no side effects.
Attacks that exploit this kind of access
Retrieves all custom fields available in Jira. Shows custom field names, IDs (e.g., customfield_10071), and types. Useful for discovering what custom fields exist and their identifiers. It is categorised as a Read tool in the Mcp Jira Stdio MCP Server, which means it retrieves data without modifying state.
jira_get_custom_fields accepts 1 parameter: projectKey. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Jira Stdio 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 Stdio. 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 Stdio MCP server (mcp-jira-stdio). 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 →