issueCreation_resetState

THE RISK

Medium Risk

Why issueCreation_resetState needs a policy

The tool modifies wizard state data (selections, field values) in a reversible manner—users can restart the wizard and re-enter selections. This is a Write operation rather than Destructive because: (1) it only affects ephemeral wizard state, not persistent Jira data; (2) it's a normal part of the wizard lifecycle; (3) the effect is easily recoverable by the user simply re-entering data.

From the tool's definition Tool description states it 'Resets the issue creation wizard state completely, clearing any selected project, issue type, or field values.' This modifies the internal state of the wizard workflow by clearing selections and values.

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

POLICY

How to control issueCreation_resetState

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_resetState:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "issueCreation_resetState": {
      "limits": [
        {
          "counter": "issuecreation_resetstate_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

issueCreation_resetState stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. 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.

LIMIT 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_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 Read analyzeJiraIssue Performs comprehensive analysis of a Jira issue

All 19 Jira MCP Toolset tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about issueCreation_resetState

What does the issueCreation_resetState tool do? +

Resets the issue creation wizard state completely, clearing any selected project, issue type, or field values. Stops any ongoing wizard process. It is categorised as a Write tool in the Jira MCP Toolset MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on issueCreation_resetState? +

Register the Jira MCP Toolset MCP server in PolicyLayer and add a rule for issueCreation_resetState: 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_resetState? +

issueCreation_resetState is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit issueCreation_resetState? +

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

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

issueCreation_resetState 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.

Enforce policy on every Jira MCP Toolset tool call.

Start from Jira MCP Toolset, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →