// MCP TOOL REFERENCE

Low Risk

issueCreation_getFields

ServerJira MCP Toolset
CategoryRead

How to control issueCreation_getFields ↓

WHAT IT DOES

What issueCreation_getFields does on Jira MCP Toolset

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

THE RISK

Low Risk

Why issueCreation_getFields needs a policy

This tool only fetches metadata about fields available for a given project and issue type. It has no side effects — it does not create, modify, or delete any data. It is purely a read/query operation to support the issue creation wizard workflow.

From the tool's definition Retrieve the available fields required for the currently selected project and issue type

Documented attack patterns abuse exactly the kind of access issueCreation_getFields gives an agent:

POLICY

How to control issueCreation_getFields

PolicyLayer is an MCP gateway — it sits between your AI agents and Jira MCP Toolset, and nothing reaches the server without passing your rules. This is the rule we recommend for issueCreation_getFields:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "issueCreation_getFields": {}
  }
}

issueCreation_getFields is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Jira MCP Toolset — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Jira MCP Toolset tools

Write issueCreation_createIssue Finalizes the wizard process by creating a Jira issue using the currently configured state Write issueCreation_initiateState Initialize a new, empty state for the issue creation wizard. Useful for testing state pers Write issueCreation_resetState Resets the issue creation wizard state completely, clearing any selected project, issue ty Write issueCreation_setAnalysisComplete Sets the analysis complete flag for the current issue creation session Write issueCreation_setUserConfirmation Sets the user confirmation flag for the current issue creation session. CRITICAL: Wait for Write issueCreation_updateFields Update and validate specific field values in the wizard state after retrieving the necessa Write issueCreation_updateState Update the core state of the issue creation wizard. Use this to set the Write issueUpdateWizard_updateIssueFromState Update a Jira issue using the current state. This tool works in two modes: 1) Immediately

All 19 Jira MCP Toolset tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about issueCreation_getFields

What does the issueCreation_getFields tool do? +

Retrieve the available fields required for the currently selected project and issue type. IMPORTANT: Before calling this tool, always check if the wizard state (analysis.metadata) already contains the required field metadata. - Only call this tool if the state is missing, incomplete, or a force refresh is explicitly required. - Avoid redundant API calls; prefer using the existing state for efficiency and consistency. 1. Call this after selecting a project and issue type to know what information is needed, but only if the state does not already have it. 2. Inform the user of required and optional fields in a human-readable format. 3. Iteratively discuss with the user to ensure all desired fields are retrieved. 4. Do not move on to the next step until the user confirms it is OK to proceed. It is categorised as a Read tool in the Jira MCP Toolset MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on issueCreation_getFields? +

Register the Jira MCP Toolset MCP server in PolicyLayer and add a rule for issueCreation_getFields: 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 Toolset. Nothing to install.

What risk level is issueCreation_getFields? +

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

Can I rate-limit issueCreation_getFields? +

Yes. Add a rate_limit block to the issueCreation_getFields 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 issueCreation_getFields completely? +

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

issueCreation_getFields is provided by the Jira MCP Toolset MCP server (tbreeding/jira-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.