list_api_files
AI agents call list_api_files to retrieve information from Code Declaration Lookup MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to list or retrieve API files from the indexed codebase. There is no indication of modification, deletion, code execution, or financial operations. Even with an empty description, the context of a code search/indexing server and the 'list' verb strongly indicate a retrieval operation with no side effects, making this a Read category tool with low severity.
From the tool's definition Tool named 'list_api_files' on a code declaration lookup server with sibling tools like 'search_declarations' and 'list_indexed_apis' indicates it retrieves or lists file metadata.
Attacks that exploit this kind of access
list_api_files. It is categorised as a Read tool in the Code Declaration Lookup MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Code Declaration Lookup MCP Server MCP server in PolicyLayer and add a rule for list_api_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 Declaration Lookup MCP Server. Nothing to install.
list_api_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 list_api_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 list_api_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.
list_api_files is provided by the Code Declaration Lookup MCP Server MCP server (osinmv/function-lookup-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 →