AI agents call jira_get_issue_images to retrieve information from Jiraxmcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing image attachments from a Jira issue and presents them as inline content. There is no creation, modification, deletion, or execution of arbitrary code. It is a simple read operation with no potential for reversible or irreversible changes to system state. Blast radius is minimal as misuse would only expose images already accessible to the authenticated user.
From the tool's definition The tool 'jira_get_issue_images' returns image attachments for a Jira issue as inline content. The verb 'get' and the action of 'return' indicate data retrieval with no modification or deletion. No side effects are produced.
Attacks that exploit this kind of access
Return image attachments for a Jira issue as inline image content. It is categorised as a Read tool in the Jiraxmcp MCP Server, which means it retrieves data without modifying state.
Register the Jirax MCP server in PolicyLayer and add a rule for jira_get_issue_images: 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 Jiraxmcp. Nothing to install.
jira_get_issue_images 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_images 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_images. 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_images is provided by the Jirax MCP server (vaibhavpandeyvpz/jiraxmcp). 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 →