Retrieves all comments for a Jira issue. Returns comment author, content, timestamps, and visibility settings. Supports pagination for issues with many comments.
AI agents call jira_get_comments to retrieve information from Mcp Jira Stdio without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
orderBy | string | — | Sort order for comments: "created" (oldest first), "-created" (newest first) |
startAt | number | — | Index of first comment to return (for pagination) |
issueKey | string | Yes | Issue key to get comments for (e.g., PROJECT-123) |
maxResults | number | — | Maximum number of comments to return (default: 50) |
Parameters from the server's own tool schema.
This tool retrieves and queries comment data from a Jira issue with no side effects. It returns metadata (author, content, timestamps, visibility) and supports pagination for data access. No data is created, modified, deleted, or executed—only read operations occur.
From the tool's definition Tool name 'jira_get_comments' and description 'Retrieves all comments' indicate a query operation that returns data without modification. Supports pagination for retrieval only.
Attacks that exploit this kind of access
Retrieves all comments for a Jira issue. Returns comment author, content, timestamps, and visibility settings. Supports pagination for issues with many comments. It is categorised as a Read tool in the Mcp Jira Stdio MCP Server, which means it retrieves data without modifying state.
jira_get_comments accepts 4 parameters: orderBy, startAt, issueKey, maxResults. Required: issueKey. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Jira Stdio MCP server in PolicyLayer and add a rule for jira_get_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 Mcp Jira Stdio. Nothing to install.
jira_get_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_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_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_comments is provided by the Mcp Jira Stdio MCP server (mcp-jira-stdio). 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 →