List all GitHub repos currently cached in the temp folder with their disk usage.
AI agents call list_cloned_repos to retrieve information from Spring Api Intel without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a query operation that retrieves information about cached repositories and their disk usage. No data is modified, executed, or destroyed. The operation has no side effects beyond reading and reporting existing state. This is a straightforward Read category tool with low severity since exposing disk usage information about cached repos poses minimal risk.
From the tool's definition Tool description states 'List all GitHub repos currently cached' - a purely informational operation that retrieves and displays cached repository metadata without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
List all GitHub repos currently cached in the temp folder with their disk usage. It is categorised as a Read tool in the Spring Api Intel MCP Server, which means it retrieves data without modifying state.
Register the Spring Api Intel MCP server in PolicyLayer and add a rule for list_cloned_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 Spring Api Intel. Nothing to install.
list_cloned_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_cloned_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_cloned_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_cloned_repos is provided by the Spring Api Intel MCP server (mparth14/spring-api-intel-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 →