explain_architectural_decisions

Explain which accepted ADRs apply before creating code (auth, payments, currency, etc.).

Server BLUEPRINT MCP vedv7/blueprint.mcp
Category Read
Risk class Low
Parameters 00 required

What explain_architectural_decisions does on BLUEPRINT MCP

AI agents call explain_architectural_decisions to retrieve information from BLUEPRINT MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why explain_architectural_decisions needs a policy

This tool reads and returns architectural decision records to inform coding decisions. It retrieves existing data (ADRs) without modifying, deleting, or executing operations. The advisory-first guidance nature confirms it is informational only. No destructive, financial, or execution-level risk.

From the tool's definition Tool description states 'Explain which accepted ADRs apply' — a pure lookup/query operation. The name uses 'explain' and sibling tools include 'list_architectural_decisions' and 'find_existing_abstractions', confirming this is a retrieval function with no…

Questions about explain_architectural_decisions

What does the explain_architectural_decisions tool do? +

Explain which accepted ADRs apply before creating code (auth, payments, currency, etc.). It is categorised as a Read tool in the BLUEPRINT MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on explain_architectural_decisions? +

Register the BLUEPRINT MCP server in PolicyLayer and add a rule for explain_architectural_decisions: 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 BLUEPRINT MCP. Nothing to install.

What risk level is explain_architectural_decisions? +

explain_architectural_decisions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit explain_architectural_decisions? +

Yes. Add a rate_limit block to the explain_architectural_decisions 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.

How do I block explain_architectural_decisions completely? +

Set action: deny in the PolicyLayer policy for explain_architectural_decisions. 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.

What MCP server provides explain_architectural_decisions? +

explain_architectural_decisions is provided by the BLUEPRINT MCP server (vedv7/blueprint.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.