list_functions_by_file
AI agents call list_functions_by_file 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.
This tool retrieves or queries code metadata (functions organized by file) without side effects. No indication of data creation, modification, deletion, or execution. The empty description lowers confidence slightly, but the server's stated purpose and naming convention strongly suggest a passive listing operation consistent with the Read category.
From the tool's definition Tool name 'list_functions_by_file' indicates listing/retrieval operation. Server description establishes this tool is part of a code declaration lookup system that 'enables full-text search' and retrieves 'functions, classes, and other code elements' without…
Attacks that exploit this kind of access
list_functions_by_file. 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_functions_by_file: 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_functions_by_file 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_functions_by_file 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_functions_by_file. 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_functions_by_file 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 →