Check whether the codebase violates recorded architectural decisions.
AI agents call check_decision_constraints 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.
This tool retrieves and validates information against recorded decisions (a read operation with no side effects). It performs static analysis or checking of constraints, which is purely informational. No code is executed, no data is modified or deleted, and there are no financial implications. The blast radius of misuse is minimal — an agent could only obtain false constraint violation reports.
From the tool's definition The tool name and description indicate it 'Check[s] whether the codebase violates recorded architectural decisions' — a query/analysis operation that examines existing data without modifying, deleting, or executing external code.
Attacks that exploit this kind of access
Check whether the codebase violates recorded architectural decisions. It is categorised as a Read tool in the BLUEPRINT MCP MCP Server, which means it retrieves data without modifying state.
Register the BLUEPRINT MCP server in PolicyLayer and add a rule for check_decision_constraints: 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.
check_decision_constraints 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_decision_constraints 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_decision_constraints. 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_decision_constraints 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.
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 →