jira_get_my_issues
AI agents call jira_get_my_issues to retrieve information from Jira - GitHub 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 or lists existing Jira issues assigned to the current user with no modification or side effects. It is a read-only data retrieval operation. Severity is low because querying one's own issues presents minimal blast radius—no data is created, modified, or deleted, and the exposure is limited to the user's own issue visibility.
From the tool's definition Tool name 'jira_get_my_issues' indicates retrieval of issue data belonging to the user. Tool description is empty, but the name and sibling tools context (jira_search_issues, jira_transition_issue) establish this as a Jira query operation.
Attacks that exploit this kind of access
jira_get_my_issues. It is categorised as a Read tool in the Jira - GitHub MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Jira - GitHub MCP Server MCP server in PolicyLayer and add a rule for jira_get_my_issues: 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 - GitHub MCP Server. Nothing to install.
jira_get_my_issues 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_my_issues 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_my_issues. 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_my_issues is provided by the Jira - GitHub MCP Server MCP server (tamarengel/jira-github-mcp). 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 →