list_issue_assignees

THE RISK

Low Risk

Why list_issue_assignees needs a policy

This is a retrieval operation that queries and returns information about who is assigned to an issue. It has no side effects, creates no new data, executes no external commands, and does not delete or modify any resources. It falls clearly into the Read category with low severity since the blast radius of misuse is minimal—an AI agent could only retrieve already-public or authorized assignment information.

From the tool's definition The tool name 'list_issue_assignees' and description 'List assignees for a specific issue' indicate a read-only query operation that retrieves existing assignment data without modifying state.

Documented attack patterns abuse exactly the kind of access list_issue_assignees gives an agent:

POLICY

How to control list_issue_assignees

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 list_issue_assignees:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_issue_assignees": {}
  }
}

list_issue_assignees is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register AtomGit MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More AtomGit MCP Server tools

Destructive delete_issue_label Remove a label from an issue in a repository Write assign_issue Assign users to an issue in a AtomGit repository Write create_issue Create a new issue in a AtomGit repository Write create_issue_comment Create an issue comment in a AtomGit repository issue Write create_issue_labels Add labels to an issue in a repository Write create_pull_request Create a new pull request in a repository Write create_pull_request_comment Create a comment on a pull request Write create_pull_request_reply Reply to a comment on a pull request

All 22 AtomGit MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about list_issue_assignees

What does the list_issue_assignees tool do? +

List assignees for a specific issue in a AtomGit repository. It is categorised as a Read tool in the AtomGit MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_issue_assignees? +

Register the AtomGit MCP Server MCP server in PolicyLayer and add a rule for list_issue_assignees: 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.

What risk level is list_issue_assignees? +

list_issue_assignees is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_issue_assignees? +

Yes. Add a rate_limit block to the list_issue_assignees 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.

How do I block list_issue_assignees completely? +

Set action: deny in the PolicyLayer policy for list_issue_assignees. 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.

What MCP server provides list_issue_assignees? +

list_issue_assignees 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.

Enforce policy on every AtomGit MCP Server tool call.

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.

CHECK YOUR STACK →