query_assignable

THE RISK

Low Risk

Why query_assignable needs a policy

This tool performs a search/query operation that retrieves user information from Jira without creating, modifying, deleting, or executing any actions. It is a standard Read operation with minimal risk—the worst case is exposure of user/project information that is typically intended for team visibility in Jira.

From the tool's definition Tool queries assignable users via Jira's read-only API endpoint /rest/api/3/user/assignable/search. The endpoint retrieves a list of users who can be assigned to tickets, with no modification or deletion of data.

Documented attack patterns abuse exactly the kind of access query_assignable gives an agent:

POLICY

How to control query_assignable

PolicyLayer is an MCP gateway — it sits between your AI agents and Jira MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for query_assignable:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "query_assignable": {}
  }
}

query_assignable is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Jira MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Jira MCP Server tools

Destructive delete_ticket Delete a ticket on Jira on the api /rest/api/3/issue/{issueIdOrKey}. Do not use markdown i Execute execute_jql Execute a JQL query on Jira on the api /rest/api/3/search/jql. Do not use markdown in your Write add_attachment_from_confluence Add an attachment to a ticket on Jira from a Confluence page by its name on the api /rest/ Write add_attachment_from_public_url Add an attachment from a public url to a ticket on Jira on the api /rest/api/3/issue/{issu Write assign_ticket Assign a ticket on Jira on the api /rest/api/3/issue/{issueIdOrKey}/assignee. Do not use m Write create_ticket Create a ticket on Jira on the api /rest/api/3/issue. Do not use markdown in any field. Write edit_ticket Edit a ticket on Jira on the api /rest/api/3/issue/{issueIdOrKey}. Do not use markdown in Read get_all_statuses Get all the status on Jira on the api /rest/api/3/status. Do not use markdown in your quer

All 11 Jira MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about query_assignable

What does the query_assignable tool do? +

Query assignables to a ticket on Jira on the api /rest/api/3/user/assignable/search?project={project-name}. Do not use markdown in your query. It is categorised as a Read tool in the Jira MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_assignable? +

Register the Jira MCP Server MCP server in PolicyLayer and add a rule for query_assignable: 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 MCP Server. Nothing to install.

What risk level is query_assignable? +

query_assignable is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit query_assignable? +

Yes. Add a rate_limit block to the query_assignable 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.

How do I block query_assignable completely? +

Set action: deny in the PolicyLayer policy for query_assignable. 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.

What MCP server provides query_assignable? +

query_assignable is provided by the Jira MCP Server MCP server (ks-gen-ai/jira-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Jira MCP Server tool call.

Start from Jira MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →