Retrieve the branch name for a Linear issue by ID
AI agents call get_issue_git_branch_name to retrieve information from Linear 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 metadata (a git branch name) associated with a Linear issue. It has no side effects, does not modify any data, and does not trigger external operations. It is a pure data retrieval function, firmly in the Read category with low severity since exposure would only allow an agent to query existing issue information.
From the tool's definition Tool name contains 'get_' prefix and description states 'Retrieve the branch name' — both indicate a read-only operation that queries data without modification.
Attacks that exploit this kind of access
Retrieve the branch name for a Linear issue by ID. It is categorised as a Read tool in the Linear MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Linear MCP Server MCP server in PolicyLayer and add a rule for get_issue_git_branch_name: 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 Linear MCP Server. Nothing to install.
get_issue_git_branch_name 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_issue_git_branch_name 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_issue_git_branch_name. 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_issue_git_branch_name is provided by the Linear MCP Server MCP server (sylphxai/linear-mcp). 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 →