One-time analysis of a specific file or directory. Returns AST structure, complexity metrics, and detected patterns for that path only. For project-wide understanding, use get_project_blueprint instead (faster, uses learned intelligence). Use this for deep-dive analysis of a specific file you\
AI agents call analyze_codebase to retrieve information from In Memoria without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
analyze_codebase retrieves and analyzes existing code without side effects. It parses and examines code structure but does not execute it, modify files, delete data, or trigger external operations. This is purely a query/inspection operation typical of static analysis tools.
From the tool's definition Tool performs 'analysis of a specific file or directory' returning 'AST structure, complexity metrics, and detected patterns'—all read-only inspection activities with no data modification, deletion, or execution of code.
Documented attack patterns abuse exactly the kind of access analyze_codebase gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and In Memoria, and nothing reaches the server without passing your rules. This is the rule we recommend for analyze_codebase:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_codebase": {}
}
}analyze_codebase 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.
One-time analysis of a specific file or directory. Returns AST structure, complexity metrics, and detected patterns for that path only. For project-wide understanding, use get_project_blueprint instead (faster, uses learned intelligence). Use this for deep-dive analysis of a specific file you\. It is categorised as a Read tool in the In Memoria MCP Server, which means it retrieves data without modifying state.
Register the In Memoria MCP server in PolicyLayer and add a rule for analyze_codebase: 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 In Memoria. Nothing to install.
analyze_codebase 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_codebase 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_codebase. 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_codebase is provided by the In Memoria MCP server (pi22by7/in-memoria). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 In Memoria tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 In Memoria tools catalogued and risk-classified — across an index of 42,500+ MCP servers.