Lists Jira tasks assigned to the current user that are not yet completed.
AI agents call list_jira_issues to retrieve information from Enterprise AI Bridge (MCP) without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query operation that retrieves information about Jira tasks. It does not create, modify, delete, or execute any actions—it only fetches and presents data. The blast radius of misuse is minimal: an agent could retrieve unwanted information but cannot cause data loss, create unwanted changes, or trigger external operations. This qualifies as a Read operation with low severity.
From the tool's definition Tool description states it 'Lists Jira tasks assigned to the current user that are not yet completed.' The verb 'lists' indicates a retrieval operation with no modification or side effects. It queries and returns data about existing Jira issues.
Attacks that exploit this kind of access
Lists Jira tasks assigned to the current user that are not yet completed. It is categorised as a Read tool in the Enterprise AI Bridge (MCP) MCP Server, which means it retrieves data without modifying state.
Register the Enterprise AI Bridge (MCP) MCP server in PolicyLayer and add a rule for list_jira_issues: 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 Enterprise AI Bridge (MCP). Nothing to install.
list_jira_issues 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 list_jira_issues 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 list_jira_issues. 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.
list_jira_issues is provided by the Enterprise AI Bridge (MCP) MCP server (olegvasilievcs/mcp-server). 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 →