AI agents call search_tasks to retrieve information from Jira without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search operation that retrieves data from Jira without creating, modifying, deleting, or executing any side effects. It falls squarely into the Read category. The severity is low because search operations have minimal blast radius—even if an agent misuses the query syntax, it can only retrieve existing data that the authenticated user is authorized to access.
From the tool's definition 'Search Jira issues using JQL. Returns results directly without caching.' - the tool queries and retrieves issue data with no modification capability.
Attacks that exploit this kind of access
Search Jira issues using JQL. Returns results directly without caching. It is categorised as a Read tool in the Jira MCP Server, which means it retrieves data without modifying state.
Register the Jira MCP server in PolicyLayer and add a rule for search_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. Nothing to install.
search_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 search_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 search_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.
search_tasks is provided by the Jira MCP server (softspark/jira-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 →