Get details of a Jira project by key.
AI agents call jira_get_project to retrieve information from Mcp Jira Confluence Corp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves project metadata without creating, modifying, deleting, or executing operations. It is a simple data retrieval operation with minimal blast radius if misused by an AI agent, as it only exposes existing project information already accessible to the authenticated user.
From the tool's definition Tool name 'jira_get_project' and description 'Get details of a Jira project by key' indicate a retrieval operation with no side effects. The verb 'Get' and the action of retrieving project details confirms this is a read-only query.
Attacks that exploit this kind of access
Get details of a Jira project by key. It is categorised as a Read tool in the Mcp Jira Confluence Corp MCP Server, which means it retrieves data without modifying state.
Register the Mcp Jira Confluence Corp MCP server in PolicyLayer and add a rule for jira_get_project: 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 Confluence Corp. Nothing to install.
jira_get_project 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 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. 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 is provided by the Mcp Jira Confluence Corp MCP server (mshegolev/mcp-jira-confluence-corp). 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 →