Get all components for a specific Jira project.
AI agents call get_project_components to retrieve information from Mcp Atlassian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves project component metadata from Jira without creating, modifying, deleting, or executing any operations. It is a read-only query operation with minimal blast radius if misused by an AI agent—worst case being information disclosure of component names and metadata already accessible to the authenticated user.
From the tool's definition Tool name 'get_project_components' and description 'Get all components for a specific Jira project' indicate a retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
Get all components for a specific Jira project. It is categorised as a Read tool in the Mcp Atlassian MCP Server, which means it retrieves data without modifying state.
Register the Mcp Atlassian MCP server in PolicyLayer and add a rule for get_project_components: 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 Atlassian. Nothing to install.
get_project_components 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 get_project_components 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 get_project_components. 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.
get_project_components is provided by the Mcp Atlassian MCP server (voarsh2/mcp-atlassian). 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 →