AI agents call list_repositories to retrieve information from MCP Code Analysis 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 returns metadata about repositories without side effects. It performs a simple enumeration/listing operation, which is a classic Read category action. The low severity reflects minimal blast radius — listing repositories cannot cause data loss, financial impact, or unwanted code execution. Confidence is high because the description is explicit and unambiguous.
From the tool's definition Tool name is 'list_repositories' and description states 'List all tracked repositories' — a pure retrieval operation with no modification, deletion, or execution of code.
Documented attack patterns abuse exactly the kind of access list_repositories gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Code Analysis Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_repositories:
{
"version": "1",
"default": "deny",
"tools": {
"list_repositories": {}
}
}list_repositories is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all tracked repositories. It is categorised as a Read tool in the MCP Code Analysis Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Code Analysis Server MCP server in PolicyLayer and add a rule for list_repositories: 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 MCP Code Analysis Server. Nothing to install.
list_repositories 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_repositories 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_repositories. 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_repositories is provided by the MCP Code Analysis Server MCP server (johannhartmann/mcpcodeanalysis). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Code Analysis Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
44 MCP Code Analysis Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.