get_repo_critical_files
AI agents call get_repo_critical_files to retrieve information from Code Expert MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about critical files within a repository—a read-only query operation with no side effects. It does not create, modify, delete, or execute code; it merely returns data about the repository structure. The blast radius of misuse is minimal (information disclosure only). Confidence is slightly reduced due to the empty description, but the tool name and context are unambiguous.
From the tool's definition Tool name 'get_repo_critical_files' indicates retrieval of file listings or metadata. Sibling tools like 'get_repo_structure', 'get_repo_file_content', and 'list_repos' are clearly read operations that query repository information without modifying state.
Attacks that exploit this kind of access
get_repo_critical_files. It is categorised as a Read tool in the Code Expert MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Code Expert MCP Server MCP server in PolicyLayer and add a rule for get_repo_critical_files: 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 Code Expert MCP Server. Nothing to install.
get_repo_critical_files 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 get_repo_critical_files 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 get_repo_critical_files. 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.
get_repo_critical_files is provided by the Code Expert MCP Server MCP server (lfnovo/code-expert-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 →