Search Jira using JQL.
AI agents call jira_search to retrieve information from Work Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries Jira issues based on search criteria; it has no side effects on the system. It matches the 'Read' category definition: searches, queries, and fetches data without creating, modifying, deleting, or triggering external operations. The blast radius of misuse is minimal—an agent could retrieve sensitive issue data, but cannot modify or delete information.
From the tool's definition Tool name 'jira_search' and description 'Search Jira using JQL' indicate a query operation that retrieves data. JQL (Jira Query Language) is a read-only query mechanism for searching existing issues.
Attacks that exploit this kind of access
Search Jira using JQL. It is categorised as a Read tool in the Work Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Work Integrations MCP server in PolicyLayer and add a rule for jira_search: 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 Work Integrations MCP. Nothing to install.
jira_search 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_search 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_search. 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_search is provided by the Work Integrations MCP server (nazarky/workspace-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 →