Lists all members of a specific Jira project
AI agents call jira_list_project_members to retrieve information from Jira MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about project membership without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with minimal risk, assuming project membership is not sensitive in the threat model. The blast radius of misuse is limited to information disclosure about who has access to a project.
From the tool's definition Tool name 'jira_list_project_members' and description 'Lists all members of a specific Jira project' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Lists all members of a specific Jira project. It is categorised as a Read tool in the Jira MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Jira MCP Server MCP server in PolicyLayer and add a rule for jira_list_project_members: 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 Jira MCP Server. Nothing to install.
jira_list_project_members 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_list_project_members 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_list_project_members. 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_list_project_members is provided by the Jira MCP Server MCP server (samuelrizzo/jira-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 →