Get details of a specific pull request comment
AI agents call get_pull_request_comment 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 retrieves information about an existing pull request comment. The verb 'Get' and the absence of any modification, deletion, or execution language clearly indicate a read-only operation. There is no potential to modify data, execute code, delete resources, or incur financial obligations.
From the tool's definition Tool name 'get_pull_request_comment' and description 'Get details of a specific pull request comment' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_pull_request_comment 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 get_pull_request_comment:
{
"version": "1",
"default": "deny",
"tools": {
"get_pull_request_comment": {}
}
} get_pull_request_comment 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.
Get details of a specific pull request comment. 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 get_pull_request_comment: 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.
get_pull_request_comment 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 get_pull_request_comment 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 get_pull_request_comment. 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.
get_pull_request_comment 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.