Create a Blueprint — a governance contract that defines validation rules. A Blueprint tells the platform what "correct" means for your data: which fields exist, what math must hold between them, and what value ranges are acceptable. Without a Blueprint, the platform has nothing to validate agains...
Risk signalsHandles credentials or secrets (api_key) · High parameter count (16 properties)
Part of the Governance Platform server.
Free to start. No card required.
AI agents use create_blueprint to create or modify resources in Governance Platform. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call create_blueprint repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Governance Platform.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"create_blueprint": {
"limits": [
{
"counter": "create_blueprint_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Governance Platform policy for all 31 tools.
These attack patterns abuse exactly the kind of access create_blueprint gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Create a Blueprint — a governance contract that defines validation rules. A Blueprint tells the platform what "correct" means for your data: which fields exist, what math must hold between them, and what value ranges are acceptable. Without a Blueprint, the platform has nothing to validate against. If you don't know what rules to define, use load_rule_pack to start from a prebuilt template, or use discover_patterns to find rules from your data. Use the blueprint_guide prompt for the complete reference of all available rule types, constraint types, and configuration options. Args: api_key: GeodesicAI API key (starts with gai_) customer_name: Organization or project name (used for folder naming) workflow_name: Unique identifier for this Blueprint (used as the 'blueprint' parameter in validate) mode: "observe" (platform checks agent's work) or "enforce" (platform computes derived fields) extracted_fields: Fields the agent extracts from source data (e.g. ["vendor", "qty", "unit_cost"]) derived_fields: Fields computed from other fields (e.g. ["subtotal", "total"]) derivation_rules: Math rules defining field relationships. Available types: "add" (target = a + b), "subtract" (target = a - b), "multiply" (target = a × b), "divide" (target = a ÷ b), "round" (round field to N places), "copy" (copy source to target), "items_multiply" (per-item a × b in a list), "items_sum" (sum a field across list items). Each rule requires "type" and the relevant fields. See blueprint_guide prompt for full schema. formal_constraints: Value bounds and ratio constraints. Available types: "magnitude_anchor" (field within min/max range, requires "field", "min", "max"), "relative_anchor" (ratio a/b within tolerance, requires "a", "b", "expected_ratio", "tolerance"), "max_action_threshold" (trigger action if field exceeds threshold, requires "field", "threshold", "action"). See blueprint_guide prompt for full schema. semantic_checks: Domain-specific validation checks require_math: Validate mathematical relationships (default true) require_consistency: Check internal consistency (default true) require_coherence: Check structural coherence (default true) require_provenance: Require agents to report extraction source locations require_high_assurance: Strictest validation — feasibility, spectral, and global consistency required enable_anomaly_detection: Geometric fingerprinting to detect structural outliers enable_drift_tracking: Monitor pattern stability across batches. It is categorised as a Write tool in the Governance Platform MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Governance Platform MCP server in PolicyLayer and add a rule for create_blueprint: 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 Governance Platform. Nothing to install.
create_blueprint is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_blueprint 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 create_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.
create_blueprint is provided by the Governance Platform MCP server (https://app.geodesiclabs.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 31 Governance Platform tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.