Move issue(s) to Jira backlog (POST /rest/agile/1.0/backlog/issue or /rest/agile/1.0/backlog/{boardId}/issue)
AI agents use addIssuesToBacklog to create or update resources in MCP Atlassian Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Atlassian Server environment.
This tool creates or modifies data reversibly (moving issues in Jira's backlog management system). It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or involve financial transactions (would be Financial). The POST operation changes issue status/location but the change can be undone, fitting the Write category.
From the tool's definition Tool description states 'Move issue(s) to Jira backlog' using POST requests to Jira Agile API endpoints. This modifies the state and location of issues within Jira, but does not delete or destroy data—the operation is reversible by moving issues to another…
Documented attack patterns abuse exactly the kind of access addIssuesToBacklog gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Atlassian Server, and nothing reaches the server without passing your rules. This is the rule we recommend for addIssuesToBacklog:
{
"version": "1",
"default": "deny",
"tools": {
"addIssuesToBacklog": {
"limits": [
{
"counter": "addissuestobacklog_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}addIssuesToBacklog 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.
Move issue(s) to Jira backlog (POST /rest/agile/1.0/backlog/issue or /rest/agile/1.0/backlog/{boardId}/issue). It is categorised as a Write tool in the MCP Atlassian Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Atlassian Server MCP server in PolicyLayer and add a rule for addIssuesToBacklog: 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 MCP Atlassian Server. Nothing to install.
addIssuesToBacklog 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 addIssuesToBacklog 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 addIssuesToBacklog. 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.
addIssuesToBacklog is provided by the MCP Atlassian Server MCP server (phuc-nt/mcp-atlassian-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 24 MCP Atlassian Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
24 MCP Atlassian Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.