Search for specific code structures like functions, classes and methods
AI agents call code_structure_search to retrieve information from CodeSeeker-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries code metadata (functions, classes, methods) without side effects. It is analogous to grep or AST inspection—passive analysis only. No data is written, executed, or destroyed. The low severity reflects that misuse would only surface incorrect search results, not cause harm to systems or data.
From the tool's definition Tool description states it 'Search[es] for specific code structures like functions, classes and methods' — a pure query operation with no modification, deletion, or execution of code.
Documented attack patterns abuse exactly the kind of access code_structure_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CodeSeeker-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for code_structure_search:
{
"version": "1",
"default": "deny",
"tools": {
"code_structure_search": {}
}
} code_structure_search 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.
Search for specific code structures like functions, classes and methods. It is categorised as a Read tool in the CodeSeeker-MCP MCP Server, which means it retrieves data without modifying state.
Register the CodeSeeker- MCP server in PolicyLayer and add a rule for code_structure_search: 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 CodeSeeker-MCP. Nothing to install.
code_structure_search 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 code_structure_search 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 code_structure_search. 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.
code_structure_search is provided by the CodeSeeker- MCP server (mixelpixx/codeseeker-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CodeSeeker-MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 CodeSeeker-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.