Medium Risk

ambr_create_contract

Generate a Ricardian Contract from a template. Creates a dual-format contract (human-readable legal text + machine-parsable JSON) using AI, linked by SHA-256 hash. The contract is stored on Ambr and accessible via the Reader Portal. Requires a valid API key (X-API-Key header on the HTTP request) ...

Risk signalsAccepts raw HTML/template content (template)

Part of the Ambr server.

ambr_create_contract can modify Ambr data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE AMBR →

Free to start. No card required.

AI agents use ambr_create_contract to create or modify resources in Ambr. 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 ambr_create_contract 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 Ambr.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "ambr_create_contract": {
      "limits": [
        {
          "counter": "ambr_create_contract_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Ambr policy for all 6 tools.

Get this rule live on your own Ambr server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY AMBR →

These attack patterns abuse exactly the kind of access ambr_create_contract gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so ambr_create_contract only ever does what you allow.

SECURE AMBR →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the ambr_create_contract tool do? +

Generate a Ricardian Contract from a template. Creates a dual-format contract (human-readable legal text + machine-parsable JSON) using AI, linked by SHA-256 hash. The contract is stored on Ambr and accessible via the Reader Portal. Requires a valid API key (X-API-Key header on the HTTP request) with available credits. Use ambr_list_templates first to discover templates and their required parameters. Args: - template (string, required): Template slug (e.g. "c1-agent-delegation") - parameters (object, required): Template-specific parameters matching the schema - principal_declaration (object, required): { agent_id, principal_name, principal_type } - parent_contract_hash (string, optional): SHA-256 hash of parent contract for amendments - amendment_type (string, optional): "original" | "amendment" | "extension" Returns: - contract_id: Unique ID (e.g. "amb-2026-0042") - sha256_hash: SHA-256 hash for verification - status: Contract status - reader_url: URL to view in Reader Portal - credits_remaining: Remaining API credits Legibility: Output is dual-format by construction and replayable to the original SHA-256 hash — the basis of Ambr's legibility guarantee.. It is categorised as a Write tool in the Ambr MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ambr_create_contract? +

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

What risk level is ambr_create_contract? +

ambr_create_contract is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit ambr_create_contract? +

Yes. Add a rate_limit block to the ambr_create_contract 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 ambr_create_contract completely? +

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

ambr_create_contract is provided by the Ambr MCP server (https://getamber.dev/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ambr tool call.

Deterministic rules across all 6 Ambr 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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.