Get comments for a specific Jira ticket
AI agents call get_comments to retrieve information from Jira MCP Server for Cursor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing comments from a Jira ticket without modifying, creating, or deleting any data. It is a read-only query operation with minimal security risk, assuming the user has appropriate access controls to view the ticket.
From the tool's definition Tool name 'get_comments' and description 'Get comments for a specific Jira ticket' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get comments for a specific Jira ticket. It is categorised as a Read tool in the Jira MCP Server for Cursor MCP Server, which means it retrieves data without modifying state.
Register the Jira MCP Server for Cursor MCP server in PolicyLayer and add a rule for 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 Jira MCP Server for Cursor. Nothing to install.
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 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 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.
get_comments is provided by the Jira MCP Server for Cursor MCP server (kornbed/jira-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_comments is one line of Jira MCP Server for Cursor's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →