Validate and preview an agent blueprint BEFORE uploading to Invarium. This runs schema validation, confidence scoring, and a full static audit locally — nothing is sent to the Invarium backend. Use this to review the blueprint with the user before calling invarium_upload_blueprint. IMPORTANT: A...
Part of the Invarium MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke invarium_prepare_blueprint to trigger processes or run actions in Invarium. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
invarium_prepare_blueprint can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
invarium_prepare_blueprint:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Invarium policy for all 19 tools.
Agents calling execute-class tools like invarium_prepare_blueprint have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
invarium_prepare_blueprint is one of the high-risk operations in Invarium. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Validate and preview an agent blueprint BEFORE uploading to Invarium. This runs schema validation, confidence scoring, and a full static audit locally — nothing is sent to the Invarium backend. Use this to review the blueprint with the user before calling invarium_upload_blueprint. IMPORTANT: Always call this tool first when a user wants to register or update an agent. Show the results to the user and ask for confirmation before proceeding with invarium_upload_blueprint. WHEN TO USE: Phase 1, Step 1 — whenever the user wants to register, update, or audit their agent's blueprint. AFTER THIS: Present the audit score and findings. Suggest specific improvements. Ask: "Want to fix any of these before uploading, or upload as-is?" If user improves, re-run this tool to show the new score. Args: blueprint: YAML string of the agent blueprint. agent_name: Optional agent name override. Falls back to blueprint field.. It is categorised as a Execute tool in the Invarium MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for invarium_prepare_blueprint. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Invarium MCP server.
invarium_prepare_blueprint is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the invarium_prepare_blueprint rule in your Intercept 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 Intercept policy for invarium_prepare_blueprint. 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.
invarium_prepare_blueprint is provided by the Invarium MCP server (invarium-ai/invarium). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept