get_only_ticket_name_and_description

THE RISK

Low Risk

Why get_only_ticket_name_and_description needs a policy

This tool retrieves and queries ticket data without creating, modifying, deleting, or executing any side effects. It is a pure read operation that fetches ticket names and descriptions. No data is changed, no code is executed, and no resources are consumed beyond the query itself.

From the tool's definition Tool name 'get_only_ticket_name_and_description' and description 'Get the name and description of the requested tickets' indicate a retrieval operation with no modifications. Uses a read-only search endpoint (/rest/api/3/search/jql) to fetch ticket metadata.

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

POLICY

How to control get_only_ticket_name_and_description

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 get_only_ticket_name_and_description:

policy.json

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

get_only_ticket_name_and_description 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 get_only_ticket_name_and_description

What does the get_only_ticket_name_and_description tool do? +

Get the name and description of the requested tickets on the api /rest/api/3/search/jql. 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 get_only_ticket_name_and_description? +

Register the Jira MCP Server MCP server in PolicyLayer and add a rule for get_only_ticket_name_and_description: 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 get_only_ticket_name_and_description? +

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

Can I rate-limit get_only_ticket_name_and_description? +

Yes. Add a rate_limit block to the get_only_ticket_name_and_description 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 get_only_ticket_name_and_description completely? +

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

get_only_ticket_name_and_description 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 →