Lists all registered codebases and their status.
AI agents call list_codebases to retrieve information from Python Codebase Analysis RAG System 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 that retrieves metadata about registered codebases. It has no side effects, does not execute code, does not modify data, and does not delete anything. The blast radius of misuse is minimal—an AI agent could only learn what codebases are registered, which is low-risk information disclosure.
From the tool's definition Tool name 'list_codebases' and description 'Lists all registered codebases and their status' indicate a query operation that retrieves and presents information without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Lists all registered codebases and their status. It is categorised as a Read tool in the Python Codebase Analysis RAG System MCP Server, which means it retrieves data without modifying state.
Register the Python Codebase Analysis RAG System MCP server in PolicyLayer and add a rule for list_codebases: 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 Python Codebase Analysis RAG System. Nothing to install.
list_codebases 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_codebases 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_codebases. 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_codebases is provided by the Python Codebase Analysis RAG System MCP server (shervinemp/codebasemcp). 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 →