Retrieves create metadata for a project, showing all available fields (including custom fields) for creating issues. Shows required vs optional fields, field types, and allowed values. Use this before creating issues to discover what fields are needed.
AI agents call jira_get_create_meta to retrieve information from Mcp Jira Stdio without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
projectKey | string | Yes | Project key to get create metadata for |
issueTypeName | string | — | Specific issue type name to get metadata for (optional) |
Parameters from the server's own tool schema.
This tool queries and returns metadata about issue creation fields without modifying, creating, or deleting any data. It is purely informational and used to discover schema information before other operations. This is a classic Read category tool—no blast radius from misuse beyond potentially exposing field structure information.
From the tool's definition Tool description states it 'Retrieves create metadata' and 'Shows' available fields, field types, and allowed values.
Attacks that exploit this kind of access
Retrieves create metadata for a project, showing all available fields (including custom fields) for creating issues. Shows required vs optional fields, field types, and allowed values. Use this before creating issues to discover what fields are needed. It is categorised as a Read tool in the Mcp Jira Stdio MCP Server, which means it retrieves data without modifying state.
jira_get_create_meta accepts 2 parameters: projectKey, issueTypeName. Required: projectKey. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Jira Stdio MCP server in PolicyLayer and add a rule for jira_get_create_meta: 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 Mcp Jira Stdio. Nothing to install.
jira_get_create_meta 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_get_create_meta 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_get_create_meta. 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_get_create_meta is provided by the Mcp Jira Stdio MCP server (mcp-jira-stdio). 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 →