confirm_receipt · CoupleHub MCP Server MCP: Risk & Policy

WHAT IT DOES

What confirm_receipt does on CoupleHub MCP Server

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

WHY IT NEEDS A POLICY

Why confirm_receipt needs a policy

The tool updates a receipt's confirmation status, which is a write operation that modifies data. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or simply read data (Read). The severity is low because confirming a receipt is a normal, low-risk operation in the context of a couples' shared household app with minimal blast radius.

From the tool's definition Tool description: 'Mark receipt confirmed' — this modifies state by marking a receipt record with a confirmation status. This is a reversible state change (can theoretically be unmarked or updated later).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

confirm_receipt Rate-limited

confirm_receipt 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": {
    "confirm_receipt": {
      "limits": [
        {
          "counter": "confirm_receipt_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 CoupleHub MCP Server, so you can run agents against it safely.

FAQ

Questions about confirm_receipt

What does the confirm_receipt tool do? +

RECEIPT STEP 3. Mark receipt confirmed. Only after user approves parsed details. It is categorised as a Write tool in the CoupleHub MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on confirm_receipt? +

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

What risk level is confirm_receipt? +

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

Can I rate-limit confirm_receipt? +

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

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

confirm_receipt is provided by the CoupleHub MCP Server MCP server (uczesieweba/couplehub-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.