add_recipient · QuickContract MCP: Risk & Policy

WHAT IT DOES

What add_recipient does on QuickContract MCP

AI agents use add_recipient to create or update resources in QuickContract MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your QuickContract MCP environment.

WHY IT NEEDS A POLICY

Why add_recipient needs a policy

This tool creates or modifies contract data reversibly—a recipient can typically be removed or modified later. It does not execute external commands, delete data irreversibly, or move funds directly. However, severity is high because recipient modifications in an escrow/contract system can redirect financial flows and create binding obligations.

From the tool's definition Tool description states 'Add a recipient to a contract,' which modifies contract state by adding a party. Within the QuickContract domain (contracts, escrow, on-chain proofs), adding recipients alters contractual obligations and fund flows.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_recipient Rate-limited

add_recipient stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_recipient": {
      "limits": [
        {
          "counter": "add_recipient_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches QuickContract MCP, so you can run agents against it safely.

FAQ

Questions about add_recipient

What does the add_recipient tool do? +

Add a recipient to a contract. kind=\. It is categorised as a Write tool in the QuickContract MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_recipient? +

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

What risk level is add_recipient? +

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

Can I rate-limit add_recipient? +

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

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

add_recipient is provided by the QuickContract MCP server (quickcontractio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.