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.
The 'get_' prefix and 'images' object indicate a read-only query operation that retrieves image assets from issues. While the empty description reduces confidence slightly, the naming pattern and server context (Atlassian Jira/Confluence) point to a data retrieval function with no side effects. Misuse would expose image data but cannot alter, delete, or execute operations.
From the tool's definition Tool name 'get_issue_images' indicates a retrieval operation. The description is empty, but the name and context (sibling tools like 'get_attachments', 'download_attachment', 'get_activities') strongly suggest this retrieves image data associated with Jira…
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 (voarsh2/mcp-atlassian). 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 →