list_repos
AI agents call list_repos 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.
The tool retrieves a list of repositories without modifying, deleting, or executing operations. The naming convention and placement among other read operations (get_*, list_*, commit_log, compare) establishes this as a data retrieval operation with no side effects. Despite the empty description, the name and context provide sufficient evidence for high confidence classification.
From the tool's definition Tool name 'list_repos' combined with server context showing 'branch listing' and repository management operations indicates a query/retrieval function.
Attacks that exploit this kind of access
list_repos. 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_repos: 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_repos 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_repos 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_repos. 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_repos 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.
list_repos 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 →