Get fields available for a specific issue type in a project
AI agents call getJiraIssueTypeMetaWithFields to retrieve information from Atlassian Multi without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns metadata about available fields for a Jira issue type. It has no side effects, does not execute code, does not modify data, and does not commit financial transactions. It is a straightforward read operation that retrieves configuration information.
From the tool's definition Tool name contains 'get' and description states 'Get fields available' — purely retrieves metadata about issue type fields without modifying or executing anything.
Attacks that exploit this kind of access
Get fields available for a specific issue type in a project. It is categorised as a Read tool in the Atlassian Multi MCP Server, which means it retrieves data without modifying state.
Register the Atlassian Multi MCP server in PolicyLayer and add a rule for getJiraIssueTypeMetaWithFields: 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 Atlassian Multi. Nothing to install.
getJiraIssueTypeMetaWithFields 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 getJiraIssueTypeMetaWithFields 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 getJiraIssueTypeMetaWithFields. 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.
getJiraIssueTypeMetaWithFields is provided by the Atlassian Multi MCP server (ntlongctt/atlassian-multi-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 →