Add issues to a Jira sprint (POST /rest/agile/1.0/sprint/{sprintId}/issue)
AI agents use addIssueToSprint 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 modifies sprint contents by adding issues, which is reversible (issues can be removed from sprints). It does not delete data, execute arbitrary code, or transfer funds. The Write category applies because it creates or modifies data reversibly. Severity is medium because misuse could disrupt sprint planning and project workflows, but the action is undoable and doesn't cause data loss or financial impact.
From the tool's definition Tool description states 'Add issues to a Jira sprint' and uses POST method, which creates/modifies project management data by assigning issues to sprints.
Documented attack patterns abuse exactly the kind of access addIssueToSprint 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 addIssueToSprint:
{
"version": "1",
"default": "deny",
"tools": {
"addIssueToSprint": {
"limits": [
{
"counter": "addissuetosprint_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}addIssueToSprint 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.
Add issues to a Jira sprint (POST /rest/agile/1.0/sprint/{sprintId}/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 addIssueToSprint: 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.
addIssueToSprint 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 addIssueToSprint 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 addIssueToSprint. 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.
addIssueToSprint 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.