Check if a user can be assigned to an issue in a AtomGit repository
AI agents call check_if_user_is_assignable to retrieve information from AtomGit MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a permission or eligibility check on user data. It retrieves or queries information (whether a user is assignable) with no side effects, data modifications, or external operations triggered. It belongs firmly in the Read category with low severity since misuse would only expose permission metadata without enabling unauthorized actions.
From the tool's definition Tool name 'check_if_user_is_assignable' and description 'Check if a user can be assigned to an issue' indicate a query operation that verifies user eligibility without modifying state.
Documented attack patterns abuse exactly the kind of access check_if_user_is_assignable 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 check_if_user_is_assignable:
{
"version": "1",
"default": "deny",
"tools": {
"check_if_user_is_assignable": {}
}
}check_if_user_is_assignable is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check if a user can be assigned to an 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.
Register the AtomGit MCP Server MCP server in PolicyLayer and add a rule for check_if_user_is_assignable: 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.
check_if_user_is_assignable is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_if_user_is_assignable 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 check_if_user_is_assignable. 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.
check_if_user_is_assignable 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.