claim_start

Signal that work has started on an escrowed task.

SERVERRemit Md MCP Server SOURCEpay-skill/mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/pay-skill-mcp/claim-start.md

WHAT IT DOES

What claim_start does on Remit Md MCP Server

AI agents invoke claim_start to trigger actions in Remit Md MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why claim_start is rated High

This tool signals state transitions in a financial escrow, which is an Execute action because it triggers consequences in an external financial system whose effects depend on context (which escrow, which user). While financial in nature, the tool itself does not move money or create obligations—it signals work initiation within an existing escrow framework.

From the tool's definition 'Signal that work has started on an escrowed task' indicates state-change operation on a financial escrow contract; combined with server context 'financial transactions such as...escrows' shows this triggers external financial system behavior.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs claim_start safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Remit Md MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For claim_start, this is the rule to start with:

claim_start Rate-limited

claim_start stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "claim_start": {
      "limits": [
        {
          "counter": "claim_start_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Remit Md MCP Server, apply this rule, and every claim_start call is checked against it from then on.

FAQ

Questions about claim_start

What does the claim_start tool do? +

Signal that work has started on an escrowed task. It is categorised as a Execute tool in the Remit Md MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on claim_start? +

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

What risk level is claim_start? +

claim_start is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit claim_start? +

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

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

claim_start is provided by the Remit Md MCP Server MCP server (pay-skill/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Remit Md MCP Server, and thousands of servers like it.

This server

All 28 Remit Md MCP Server tools → High-risk tools on this server →

Across the catalogue

start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →