Low Risk

fund_bounty_escrow

Charge your saved payment method to fund a bounty's escrow. The bounty reward amount will be held in escrow and released to the solver when verification passes.

Part of the ArcAgent MCP server.

fund_bounty_escrow is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE ARCAGENT MCP →

Free to start. No card required.

AI agents call fund_bounty_escrow to retrieve information from ArcAgent MCP without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though fund_bounty_escrow only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "fund_bounty_escrow": {}
  }
}

See the full ArcAgent MCP policy for all 45 tools.

Get this rule live on your own ArcAgent MCP server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY ARCAGENT MCP →

View all 45 tools →

These attack patterns abuse exactly the kind of access fund_bounty_escrow gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so fund_bounty_escrow only ever does what you allow.

SECURE ARCAGENT MCP →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the fund_bounty_escrow tool do? +

Charge your saved payment method to fund a bounty's escrow. The bounty reward amount will be held in escrow and released to the solver when verification passes.. It is categorised as a Read tool in the ArcAgent MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fund_bounty_escrow? +

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

What risk level is fund_bounty_escrow? +

fund_bounty_escrow is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit fund_bounty_escrow? +

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

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

fund_bounty_escrow is provided by the ArcAgent MCP server (araujota/arcagent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ArcAgent MCP tool call.

Deterministic rules across all 45 ArcAgent MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.