Extract and analyze symbols (functions, classes, etc.) from code files
AI agents call analyze_file_symbols to retrieve information from ZMCPTools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs static code analysis to extract syntactic information (functions, classes, symbols) from source files. It reads and parses code without executing it, modifying files, or causing side effects. This is a pure read operation that queries code structure metadata, fitting the Read category pattern of 'get, fetch, analyze' operations.
From the tool's definition Tool name 'analyze_file_symbols' and description 'Extract and analyze symbols (functions, classes, etc.) from code files' indicate data retrieval and analysis with no modification or execution of code.
Documented attack patterns abuse exactly the kind of access analyze_file_symbols gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ZMCPTools, and nothing reaches the server without passing your rules. This is the rule we recommend for analyze_file_symbols:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_file_symbols": {}
}
}analyze_file_symbols 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.
Extract and analyze symbols (functions, classes, etc.) from code files. It is categorised as a Read tool in the ZMCPTools MCP Server, which means it retrieves data without modifying state.
Register the ZMCPTools MCP server in PolicyLayer and add a rule for analyze_file_symbols: 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 ZMCPTools. Nothing to install.
analyze_file_symbols 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 analyze_file_symbols 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 analyze_file_symbols. 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.
analyze_file_symbols is provided by the ZMCPTools MCP server (zachhandley/zmcptools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 70 ZMCPTools tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
70 ZMCPTools tools catalogued and risk-classified — across an index of 42,500+ MCP servers.