list_jira_custom_field_options

list_jira_custom_field_options

Server DCI MCP Server redhat-community-ai-tools/dci-mcp-server
Category Read
Risk class Low
Parameters 00 required

What list_jira_custom_field_options does on DCI MCP Server

AI agents call list_jira_custom_field_options to retrieve information from DCI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why list_jira_custom_field_options needs a policy

This tool retrieves metadata about Jira custom field options, which is a non-destructive query operation. There is no indication it modifies, deletes, or executes any operations. Confidence is slightly reduced (0.75 rather than higher) due to the empty description, which prevents confirmation of side effects, but the name strongly indicates a list/retrieval function typical of Read category tools.

From the tool's definition Tool name 'list_jira_custom_field_options' indicates retrieving or enumerating custom field options from Jira without modifying them. The absence of verbs like 'create', 'update', 'delete', or 'execute' suggests read-only data retrieval.

Questions about list_jira_custom_field_options

What does the list_jira_custom_field_options tool do? +

list_jira_custom_field_options. It is categorised as a Read tool in the DCI MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_jira_custom_field_options? +

Register the DCI MCP Server MCP server in PolicyLayer and add a rule for list_jira_custom_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 DCI MCP Server. Nothing to install.

What risk level is list_jira_custom_field_options? +

list_jira_custom_field_options is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_jira_custom_field_options? +

Yes. Add a rate_limit block to the list_jira_custom_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.

How do I block list_jira_custom_field_options completely? +

Set action: deny in the PolicyLayer policy for list_jira_custom_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.

What MCP server provides list_jira_custom_field_options? +

list_jira_custom_field_options is provided by the DCI MCP Server MCP server (redhat-community-ai-tools/dci-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.