Create a new agile board (Scrum or Kanban). The board can be created for a specific project or based on a filter.
AI agents use jira_create_board to create or update resources in Atlassian — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Atlassian environment.
Creating a new board is a Write operation—it creates data structures (board configuration, metadata) that persist in the system. While the action is reversible (boards can be deleted), the primary effect is data creation/modification rather than destructive removal.
From the tool's definition Tool description states it will 'Create a new agile board', which is an irreversible creation action that modifies the system state by adding new resources.
Documented attack patterns abuse exactly the kind of access jira_create_board gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Atlassian, and nothing reaches the server without passing your rules. This is the rule we recommend for jira_create_board:
{
"version": "1",
"default": "deny",
"tools": {
"jira_create_board": {
"limits": [
{
"counter": "jira_create_board_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}jira_create_board 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.
Create a new agile board (Scrum or Kanban). The board can be created for a specific project or based on a filter. It is categorised as a Write tool in the Atlassian MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Atlassian MCP server in PolicyLayer and add a rule for jira_create_board: 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 Atlassian. Nothing to install.
jira_create_board 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 jira_create_board 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 jira_create_board. 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.
jira_create_board is provided by the Atlassian MCP server (xuanxt/atlassian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Atlassian, 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.
51 Atlassian tools catalogued and risk-classified — across an index of 43,000+ MCP servers.