get_issues_development_info
AI agents call get_issues_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.
The 'get_' prefix and sibling tools like 'get_agile_boards', 'get_all_projects', 'get_comments' establish a pattern of read-only retrieval operations. The tool likely retrieves development information (commits, branches, pull requests) associated with Jira issues, which would be metadata inspection with no side effects.
From the tool's definition Tool name 'get_issues_development_info' contains 'get_', which follows a read-only retrieval pattern. The description is empty, limiting direct evidence.
Attacks that exploit this kind of access
get_issues_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_issues_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_issues_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_issues_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_issues_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_issues_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.