AI agents call zig_document_symbols to retrieve information from Zig 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 code structure without modifying, executing, or deleting anything. It is a standard IDE intelligence feature that queries the language server for parsed symbol information. The retrieval of code outline data presents minimal security risk and falls cleanly into the Read category.
From the tool's definition Tool description states it 'Get[s] the document symbol outline (functions, structs, variables) of a Zig file via ZLS' — a read-only retrieval operation with no side effects.
Attacks that exploit this kind of access
Get the document symbol outline (functions, structs, variables) of a Zig file via ZLS. It is categorised as a Read tool in the Zig MCP Server, which means it retrieves data without modifying state.
Register the Zig MCP server in PolicyLayer and add a rule for zig_document_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 Zig. Nothing to install.
zig_document_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 zig_document_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 zig_document_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.
zig_document_symbols is provided by the Zig MCP server (sadopc/mcp-server-zig). 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 →