Browse accessible JIRA projects with metadata. Shows project keys, names, issue types, and components. Use this to discover which projects to sync feedback to.
AI agents call browse_jira_projects to retrieve information from ProduckAI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and displays metadata about JIRA projects—it has no capability to create, modify, delete, or execute operations. The purpose is discovery ('Use this to discover which projects') to inform downstream decisions. No side effects or state changes occur. This is a classic Read operation with low severity since viewing project metadata poses minimal security risk.
From the tool's definition Tool description states it 'Browse[s] accessible JIRA projects with metadata' and 'Shows project keys, names, issue types, and components.' These are read-only discovery operations that retrieve and display information without modification.
Attacks that exploit this kind of access
Browse accessible JIRA projects with metadata. Shows project keys, names, issue types, and components. Use this to discover which projects to sync feedback to. It is categorised as a Read tool in the ProduckAI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ProduckAI MCP Server MCP server in PolicyLayer and add a rule for browse_jira_projects: 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 ProduckAI MCP Server. Nothing to install.
browse_jira_projects 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 browse_jira_projects 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 browse_jira_projects. 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.
browse_jira_projects is provided by the ProduckAI MCP Server MCP server (rohitsaraff33-bit/produckai-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 →