Update the core state of the issue creation wizard. Use this to set the
AI agents use issueCreation_updateState to create or update resources in Jira MCP Toolset — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jira MCP Toolset environment.
The tool modifies state within the issue creation wizard workflow. While the description is incomplete ('Use this to set the' cuts off), the 'update' verb and context of state management indicate a Write operation that reversibly changes configuration or progress. It does not appear to create final Jira issues (that is handled by issueCreation_createIssue), nor does it delete data.
From the tool's definition Tool name contains 'update' and description states 'Update the core state of the issue creation wizard.' This indicates modification of internal state rather than retrieval.
Documented attack patterns abuse exactly the kind of access issueCreation_updateState gives an agent:
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_updateState:
{
"version": "1",
"default": "deny",
"tools": {
"issueCreation_updateState": {
"limits": [
{
"counter": "issuecreation_updatestate_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} issueCreation_updateState 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.
Free to start. No card required.
Update the core state of the issue creation wizard. Use this to set the. 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.
Register the Jira MCP Toolset MCP server in PolicyLayer and add a rule for issueCreation_updateState: 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.
issueCreation_updateState is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the issueCreation_updateState 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 issueCreation_updateState. 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.
issueCreation_updateState 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.
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.