Low Risk

issueCreation_getState

Get the current internal state of the issue creation wizard, including selected project, issue type, and entered field values. Useful for checking progress or debugging.

How to control issueCreation_getState ↓

What issueCreation_getState does on Jira MCP Toolset

AI agents call issueCreation_getState 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.

Low Risk

Why issueCreation_getState needs a policy

This tool only retrieves and returns the current state of the wizard session (project, issue type, field values). It performs no side effects, creates nothing, and does not modify any data. It is a pure read/inspect operation used for checking progress or debugging.

From the tool's definition Get the current internal state of the issue creation wizard, including selected project, issue type, and entered field values

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

How to control issueCreation_getState

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "issueCreation_getState": {}
  }
}

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

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about issueCreation_getState

What does the issueCreation_getState tool do? +

Get the current internal state of the issue creation wizard, including selected project, issue type, and entered field values. Useful for checking progress or debugging. 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_getState? +

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

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

Can I rate-limit issueCreation_getState? +

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

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

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

Free to start. No card required.

19 Jira MCP Toolset tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.