list_repo_branches
AI agents call list_repo_branches to retrieve information from Tangled MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Listing repository branches is a read-only operation with no side effects—it queries and retrieves data without modifying, deleting, or executing anything. This is the lowest risk classification. The tool has minimal blast radius if misused by an AI agent, as it cannot cause data loss, execution, or financial impact.
From the tool's definition Tool name 'list_repo_branches' indicates a listing operation that retrieves branch information. The server description confirms the platform 'Supports repository management, branch listing' and the sibling tools context (create, delete, update, list…
Attacks that exploit this kind of access
list_repo_branches. It is categorised as a Read tool in the Tangled MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tangled MCP Server MCP server in PolicyLayer and add a rule for list_repo_branches: 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 Tangled MCP Server. Nothing to install.
list_repo_branches 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 list_repo_branches 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 list_repo_branches. 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.
list_repo_branches is provided by the Tangled MCP Server MCP server (zzstoatzz/tangled-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 →