mark_transaction_paid · Ontraport MCP Server MCP

WHAT IT DOES

What mark_transaction_paid does on Ontraport MCP Server

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

WHY IT NEEDS A POLICY

Why mark_transaction_paid needs a policy

This is a Write operation because it updates an existing transaction record to reflect a payment status change. Though it touches financial data, it does not execute a payment transfer (which would be Financial), nor does it delete data (Destructive). The operation is reversible—the transaction status can be changed again if needed.

From the tool's definition Tool description explicitly states it 'Mark a transaction as manually paid,' which modifies transaction payment status in the Ontraport CRM system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mark_transaction_paid Rate-limited

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

FAQ

Questions about mark_transaction_paid

What does the mark_transaction_paid tool do? +

Mark a transaction as manually paid. Use when payment was received outside of the payment gateway (e.g., check, cash, wire transfer). It is categorised as a Write tool in the Ontraport 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 mark_transaction_paid? +

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

What risk level is mark_transaction_paid? +

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

Can I rate-limit mark_transaction_paid? +

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

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

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