get repository metadata: knot, default branch, languages, labels
AI agents call get_repo 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.
This tool queries and retrieves repository metadata without modifying, deleting, or executing any operations. It fits the Read category as a straightforward data retrieval operation with no mutation or side effects. Severity is low because metadata exposure poses minimal risk compared to write or destructive operations.
From the tool's definition Tool name 'get_repo' and description 'get repository metadata' indicate data retrieval with no side effects. Returns read-only information: knot, default branch, languages, labels.
Attacks that exploit this kind of access
get repository metadata: knot, default branch, languages, labels. 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 get_repo: 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.
get_repo 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_repo 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_repo. 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_repo 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.
get_repo is one line of Tangled MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →