AI agents use jira_assign_issue to create or update resources in Sage MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sage MCP environment.
This tool creates or modifies data (issue assignment) in a reversible manner. Reassigning an issue can be undone by reassigning it to someone else or back to the original assignee. While it has side effects on project workflow and notifications, the operation is not destructive (data is not deleted), does not execute arbitrary code, and does not involve financial transactions.
From the tool's definition Tool name 'jira_assign_issue' and description 'Assign an issue to a user' indicate the tool modifies issue state by reassigning ownership, which is a reversible write operation.
Documented attack patterns abuse exactly the kind of access jira_assign_issue gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for jira_assign_issue:
{
"version": "1",
"default": "deny",
"tools": {
"jira_assign_issue": {
"limits": [
{
"counter": "jira_assign_issue_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}jira_assign_issue 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.
Assign an issue to a user. It is categorised as a Write tool in the Sage MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sage MCP server in PolicyLayer and add a rule for jira_assign_issue: 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 Sage MCP. Nothing to install.
jira_assign_issue 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_assign_issue 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_assign_issue. 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_assign_issue is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.