get_issue_development_info
AI agents call get_issue_development_info 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 development information associated with a Jira issue. The 'get_' prefix and position among other retrieval tools (get_agile_boards, get_board_issues) strongly suggests it queries and returns data without modification or side effects. No create, update, delete, or execute keywords present.
From the tool's definition Tool name 'get_issue_development_info' uses 'get', indicating a retrieval operation. Description is empty, limiting direct evidence, but naming convention and context among sibling tools (get_agile_boards, get_board_issues, get_comments, download_*) all…
Attacks that exploit this kind of access
get_issue_development_info. 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_development_info: 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_development_info 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_development_info 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_development_info. 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_development_info 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.