Combined duplicate + placement check. Advisory-first by default; blocks only in enforce mode.
AI agents call verify_and_place_code 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.
The tool performs analysis (duplicate and placement checks) and returns advisory guidance. It does not create, modify, delete, or execute anything by default. The 'enforce mode' could block actions, but blocking is a read-like gate rather than a write/execute side effect. Severity is low because misuse only results in incorrect advisory output, not data loss or execution.
From the tool's definition 'Advisory-first by default; blocks only in enforce mode' and 'Combined duplicate + placement check' — the tool primarily checks and advises rather than modifying or executing code.
Attacks that exploit this kind of access
Combined duplicate + placement check. Advisory-first by default; blocks only in enforce mode. 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 verify_and_place_code: 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.
verify_and_place_code 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 verify_and_place_code 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 verify_and_place_code. 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.
verify_and_place_code 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 →