List available branches for the default project from config
AI agents call list_branches to retrieve information from Claude Context MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about available branches from configuration. It has no side effects, does not execute code, does not modify data, and does not access financial systems. It is purely informational and falls squarely into the Read category with low severity due to minimal blast radius if misused.
From the tool's definition Tool name is 'list_branches' and description states 'List available branches for the default project from config' — this is a query operation that retrieves branch information without modifying or executing anything.
Attacks that exploit this kind of access
List available branches for the default project from config. It is categorised as a Read tool in the Claude Context MCP MCP Server, which means it retrieves data without modifying state.
Register the Claude Context MCP server in PolicyLayer and add a rule for list_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 Claude Context MCP. Nothing to install.
list_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_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_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_branches is provided by the Claude Context MCP server (sahinrasit/ibtech-mcp-claude-context). 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 →