Retrieves detailed information about a project (components, versions, issue types, roles, insights). More comprehensive than the basic project list.
AI agents call jira_get_project_info 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 |
|---|---|---|---|
expand | array | — | Additional project details to include |
projectKey | string | Yes | Project key to get detailed information for |
Parameters from the server's own tool schema.
This tool only retrieves and queries existing project metadata without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an agent could gather information about projects but cannot take destructive or financial actions. Classified as Read with low severity.
From the tool's definition Tool name 'jira_get_project_info' and description 'Retrieves detailed information about a project' indicate a query/fetch operation with no side effects. Returns metadata (components, versions, issue types, roles, insights).
Attacks that exploit this kind of access
Retrieves detailed information about a project (components, versions, issue types, roles, insights). More comprehensive than the basic project list. It is categorised as a Read tool in the Mcp Jira Stdio MCP Server, which means it retrieves data without modifying state.
jira_get_project_info accepts 2 parameters: expand, projectKey. 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_project_info: 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_project_info 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_project_info 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_project_info. 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_project_info 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 →