Search across all file types - BEST FIRST CALL for targeted questions, USE INSTEAD of Grep: content_pattern finds text WITH structural context (enclosing function/class/section) plus leads to definitions; name/type/decorator find structures
AI agents call search_structures to retrieve information from Scantool - File Scanner MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
search_structures performs read-only querying and pattern matching across source code to extract structural information (functions, classes, decorators, etc.). It retrieves data with contextual information but does not modify, delete, execute, or create anything. This is a classic Read category tool—no side effects, purely informational exploration of a codebase.
From the tool's definition Tool description states it 'Search[es] across all file types' and 'find[s] structures' with 'content_pattern finds text' and 'name/type/decorator find structures'. These are query operations that retrieve and analyze source code structure.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Search across all file types - BEST FIRST CALL for targeted questions, USE INSTEAD of Grep: content_pattern finds text WITH structural context (enclosing function/class/section) plus leads to definitions; name/type/decorator find structures. It is categorised as a Read tool in the Scantool - File Scanner MCP MCP Server, which means it retrieves data without modifying state.
Register the Scantool - File Scanner MCP server in PolicyLayer and add a rule for search_structures: 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 Scantool - File Scanner MCP. Nothing to install.
search_structures 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 search_structures 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 search_structures. 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.
search_structures is provided by the Scantool - File Scanner MCP server (mariusei/file-scanner-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 →