Get the count of comments in a specific Backlog issue
AI agents call get_issue_comment_count to retrieve information from Backlog MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves metadata (comment count) from an issue without side effects. It does not create, modify, delete, or execute any operations. It is a straightforward read operation consistent with similar tools on the server like 'get_issue_detail' and 'get_issue_comments'.
From the tool's definition Tool name 'get_issue_comment_count' and description 'Get the count of comments in a specific Backlog issue' indicate a retrieval operation that returns a numeric count without modifying, deleting, or executing any actions.
Attacks that exploit this kind of access
Get the count of comments in a specific Backlog issue. It is categorised as a Read tool in the Backlog MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Backlog MCP Server MCP server in PolicyLayer and add a rule for get_issue_comment_count: 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 Backlog MCP Server. Nothing to install.
get_issue_comment_count 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_issue_comment_count 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_issue_comment_count. 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_issue_comment_count is provided by the Backlog MCP Server MCP server (katsuhirohonda/mcp-backlog-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →