get_issue_images
AI agents call get_issue_images to retrieve information from MCP Atlassian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves (does not modify or delete) image data from Jira issues. It has no side effects and poses minimal risk if called by an AI agent—worst case, it returns image metadata or binary data already accessible via normal Jira permissions. The empty description prevents higher confidence, but the naming convention and context strongly indicate a query/retrieval operation.
From the tool's definition Tool name 'get_issue_images' indicates retrieval of image data associated with Jira issues. The 'get_' prefix is a strong signal of a read-only operation.
Attacks that exploit this kind of access
get_issue_images. It is categorised as a Read tool in the MCP Atlassian MCP Server, which means it retrieves data without modifying state.
Register the MCP Atlassian MCP server in PolicyLayer and add a rule for 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 MCP Atlassian. Nothing to install.
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 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 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.
get_issue_images is provided by the MCP Atlassian MCP server (sooperset/mcp-atlassian). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.