Initialize a new, empty state for the issue creation wizard. Useful for testing state persistence across multiple tool calls. IMPORTANT: Do not jump ahead in the workflow. Always follow the steps in order and wait for the user
AI agents use issueCreation_initiateState 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.
This tool prepares state for creating issues (write operation), but does not itself create, modify, or delete actual Jira data. It sets up an empty state object for the wizard.
From the tool's definition Tool initializes a new state for the issue creation wizard, explicitly described as part of a workflow for creating issues. Paired with sibling tool issueCreation_createIssue which confirms write intent.
Documented attack patterns abuse exactly the kind of access issueCreation_initiateState 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_initiateState:
{
"version": "1",
"default": "deny",
"tools": {
"issueCreation_initiateState": {
"limits": [
{
"counter": "issuecreation_initiatestate_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}issueCreation_initiateState 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.
Initialize a new, empty state for the issue creation wizard. Useful for testing state persistence across multiple tool calls. IMPORTANT: Do not jump ahead in the workflow. Always follow the steps in order and wait for the user. 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_initiateState: 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_initiateState 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_initiateState 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_initiateState. 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_initiateState 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.