Detect architectural patterns in a codebase
AI agents call detect-architecture to retrieve information from MCP Codebase Insight without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs static analysis of codebase patterns and architectural structure, returning insights without any side effects. It reads and analyzes existing code to identify patterns, which is a safe information retrieval operation. The sibling tools (analyze-patterns, get-metrics, health-check) further confirm this server's purpose is observational analysis rather than system mutation.
From the tool's definition Tool description states it 'Detect[s] architectural patterns in a codebase' — purely analytical retrieval of existing code structure information. No creation, modification, execution, or deletion of code or data.
Documented attack patterns abuse exactly the kind of access detect-architecture gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Codebase Insight, and nothing reaches the server without passing your rules. This is the rule we recommend for detect-architecture:
{
"version": "1",
"default": "deny",
"tools": {
"detect-architecture": {}
}
}detect-architecture 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.
Detect architectural patterns in a codebase. It is categorised as a Read tool in the MCP Codebase Insight MCP Server, which means it retrieves data without modifying state.
Register the MCP Codebase Insight MCP server in PolicyLayer and add a rule for detect-architecture: 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 MCP Codebase Insight. Nothing to install.
detect-architecture 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 detect-architecture 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 detect-architecture. 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.
detect-architecture is provided by the MCP Codebase Insight MCP server (tosin2013/mcp-codebase-insight). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Codebase Insight, 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.
4 MCP Codebase Insight tools catalogued and risk-classified — across an index of 43,000+ MCP servers.