get_labels
AI agents call get_labels 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.
The 'get_' prefix indicates a read-only query operation that retrieves label data from Atlassian Jira/Confluence without modifying state. No side effects are expected. The empty description reduces confidence slightly, but the consistent naming pattern across the sibling tools and typical Atlassian API design strongly suggests this is a simple data retrieval endpoint.
From the tool's definition Tool name 'get_labels' with no description. Based on naming convention (get_*) and context among sibling tools (get_agile_boards, get_all_projects, get_board_issues, get_comments), this is a retrieval operation.
Attacks that exploit this kind of access
get_labels. 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_labels: 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_labels 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_labels 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_labels. 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_labels is provided by the MCP Atlassian MCP server (sooperset/mcp-atlassian). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.