create_contract
Create a conditional contract with escrow
This record as markdown: /tools/io-github-bbrainfrance-midas-protocol/create-contract.md
What create_contract does on MIDAS Protocol
AI agents use create_contract to commit financial operations through MIDAS Protocol, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
title | string | Yes | |
currency | string | Yes | |
conditions | array | Yes | |
description | string | Yes | |
deadlineDays | number | — | |
escrowAmount | number | Yes | |
counterpartyId | string | Yes |
Parameters from the server's own tool schema.
Why create_contract is rated Critical
Creating a contract with escrow involves binding financial commitments: funds are locked, counterparties are obligated, and financial terms are established. This is a core financial operation on a platform explicitly designed for payments, lending, and escrow. Misuse could lock an agent's or user's funds in escrow, create unintended financial obligations, or facilitate fraud.
From the tool's definition 'Create a conditional contract with escrow' — directly commits financial obligations and locks funds in escrow arrangements
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs create_contract safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MIDAS Protocol, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_contract, this is the rule to start with:
Any call to create_contract is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect MIDAS Protocol, apply this rule, and every create_contract call is checked against it from then on.
Questions about create_contract
Create a conditional contract with escrow. It is categorised as a Financial tool in the MIDAS Protocol MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
create_contract accepts 7 parameters: title, currency, conditions, description, deadlineDays, escrowAmount, counterpartyId. Required: title, currency, conditions, description, escrowAmount, counterpartyId. The full parameter table on this page comes from the server's own tool schema.
Register the MIDAS Protocol MCP server in PolicyLayer and add a rule for 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 MIDAS Protocol. Nothing to install.
create_contract is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the 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.
Set action: deny in the PolicyLayer policy for 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.
create_contract is provided by the MIDAS Protocol MCP server (https://mcp.midasprotocol.org/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MIDAS Protocol, and thousands of servers like it.
Across the catalogue