Debug tool for exploring raw JIRA data. Returns raw field data and field name mappings. Useful for finding custom field IDs.
AI agents call jira_debug_search to retrieve information from JIRA MCP Server 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 query and returns field metadata without modifying, deleting, or executing any operations. It retrieves and queries existing data for debugging purposes. The severity is low because exposure of field mappings and schema information, while potentially useful for reconnaissance, does not directly impact data integrity, availability, or financial systems. It is informational in nature.
From the tool's definition Tool description states 'Returns raw field data and field name mappings' and is characterized as a 'Debug tool for exploring raw JIRA data.' The verb is 'exploring' and 'returns,' indicating data retrieval with no modification, deletion, or execution of…
Attacks that exploit this kind of access
Debug tool for exploring raw JIRA data. Returns raw field data and field name mappings. Useful for finding custom field IDs. It is categorised as a Read tool in the JIRA MCP Server MCP Server, which means it retrieves data without modifying state.
Register the JIRA MCP Server MCP server in PolicyLayer and add a rule for jira_debug_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 JIRA MCP Server. Nothing to install.
jira_debug_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_debug_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_debug_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_debug_search is provided by the JIRA MCP Server MCP server (suppleaardvark/jira-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 →