check_architecture
Check architectural layer rules: detect forbidden imports between layers (e.g. domain importing infrastructure). Supports auto-detected presets (clean-architecture, hexagonal) or custom layers. Use to enforce architectural boundaries. Read-only. Returns JSON: { violations: [{ from, to, rule, file...
This record as markdown: /tools/nikolai-vysotskyi-trace-mcp/check-architecture.md
What check_architecture does on Trace
AI agents call check_architecture to retrieve information from Trace without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_architecture is rated Low
This tool analyzes architectural boundaries by inspecting the dependency graph to detect policy violations. It performs static analysis and returns findings without creating, modifying, deleting, or executing code. The 'detect' verb and 'returns JSON' confirm it is a read-only query operation. Low severity because misuse would only surface incorrect architectural reports, not cause damage or execution.
From the tool's definition Tool description explicitly states 'Read-only' and 'detect forbidden imports' (analysis without modification). Returns violations report in JSON. No side effects on source code.
Attacks that exploit this kind of access
The rule that runs check_architecture safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Trace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_architecture, this is the rule to start with:
check_architecture is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Trace, apply this rule, and every check_architecture call is checked against it from then on.
Questions about check_architecture
Check architectural layer rules: detect forbidden imports between layers (e.g. domain importing infrastructure). Supports auto-detected presets (clean-architecture, hexagonal) or custom layers. Use to enforce architectural boundaries. Read-only. Returns JSON: { violations: [{ from, to, rule, file, line }], total, preset }. It is categorised as a Read tool in the Trace MCP Server, which means it retrieves data without modifying state.
Register the Trace MCP server in PolicyLayer and add a rule for check_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 Trace. Nothing to install.
check_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 check_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 check_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.
check_architecture is provided by the Trace MCP server (nikolai-vysotskyi/trace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Trace, and thousands of servers like it.
This server
Across the catalogue