List all indexed repositories with project ID mapping. Use this to find which projectId to pass to code tools.
AI agents call corn_list_repos to retrieve information from CornMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation to list and map repositories. It has no side effects, does not execute code, does not modify data, and does not delete or move money. The blast radius of misuse is minimal—an agent could enumerate repositories but cannot act on that information without calling separate code analysis or execution tools. Classified as Read with low severity.
From the tool's definition Tool description states 'List all indexed repositories' — a query operation that retrieves data without modification. The name 'corn_list_repos' and description indicate enumeration of existing repositories for discovery purposes.
Documented attack patterns abuse exactly the kind of access corn_list_repos gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CornMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for corn_list_repos:
{
"version": "1",
"default": "deny",
"tools": {
"corn_list_repos": {}
}
}corn_list_repos 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 indexed repositories with project ID mapping. Use this to find which projectId to pass to code tools. It is categorised as a Read tool in the CornMCP MCP Server, which means it retrieves data without modifying state.
Register the Corn MCP server in PolicyLayer and add a rule for corn_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 CornMCP. Nothing to install.
corn_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 corn_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 corn_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.
corn_list_repos is provided by the Corn MCP server (yuki-20/cornmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 18 CornMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
18 CornMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.