Assign users to an issue in a AtomGit repository
AI agents use assign_issue to create or update resources in AtomGit MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AtomGit MCP Server environment.
Assigning a user to an issue is a reversible modification operation. It changes the issue's state by adding/updating assignee information, which qualifies as Write. Severity is medium because misconfiguration could assign wrong users to sensitive issues (creating noise or exposure), but the blast radius is limited to metadata changes on a single issue.
From the tool's definition Tool description explicitly states 'Assign users to an issue' — this modifies the assignee metadata of an issue, creating or updating an association without deleting or overwriting data irreversibly.
Documented attack patterns abuse exactly the kind of access assign_issue gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AtomGit MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for assign_issue:
{
"version": "1",
"default": "deny",
"tools": {
"assign_issue": {
"limits": [
{
"counter": "assign_issue_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} 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 users to an issue in a AtomGit repository. It is categorised as a Write tool in the AtomGit MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AtomGit MCP Server MCP server in PolicyLayer and add a rule for 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 AtomGit MCP Server. Nothing to install.
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 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 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.
assign_issue is provided by the AtomGit MCP Server MCP server (kaiyuanxiaobing/atomgit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AtomGit MCP Server, 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.
22 AtomGit MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.