AI agents call jira_my_tasks to retrieve information from Jira Dev without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data (Jira issues) for the authenticated user with optional filtering. It has no side effects—it does not create, modify, delete, or execute any operations. It is a straightforward data retrieval operation, making it a Read category tool with low severity risk.
From the tool's definition Tool name and description: 'List Jira issues assigned to the currently authenticated user, optionally filtered by status.' The verb 'List' and the function of retrieving/querying existing issues without modification or side effects clearly indicates a read…
Attacks that exploit this kind of access
List Jira issues assigned to the currently authenticated user, optionally filtered by status. It is categorised as a Read tool in the Jira Dev MCP Server, which means it retrieves data without modifying state.
Register the Jira Dev MCP server in PolicyLayer and add a rule for jira_my_tasks: 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 Jira Dev. Nothing to install.
jira_my_tasks 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_my_tasks 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_my_tasks. 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_my_tasks is provided by the Jira Dev MCP server (jira-dev-mcp). 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 →