Get comments on a specific JIRA issue. Returns comment author, body, and creation date.
AI agents call jira_get_issue_comments to retrieve information from JIRA 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 and queries comment data from JIRA issues without causing any side effects or state changes. It is a straightforward data fetch operation that fits the Read category definition of 'retrieves or queries data; no side effects'.
From the tool's definition Tool description states 'Get comments on a specific JIRA issue' and 'Returns comment author, body, and creation date' — purely retrieval operations with no modification, deletion, or execution.
Attacks that exploit this kind of access
Get comments on a specific JIRA issue. Returns comment author, body, and creation date. It is categorised as a Read tool in the JIRA MCP Server MCP Server, which means it retrieves data without modifying state.
Register the JIRA MCP Server MCP server in PolicyLayer and add a rule for jira_get_issue_comments: 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 JIRA MCP Server. Nothing to install.
jira_get_issue_comments 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 jira_get_issue_comments 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 jira_get_issue_comments. 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.
jira_get_issue_comments is provided by the JIRA MCP Server MCP server (suppleaardvark/jira-mcp-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 →