gibwork_createBounty

SERVERSap SOURCEhttps://mcp.sap.oobeprotocol.ai/mcp

Critical RISK CLASS

Category Financial

Parameters 74 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/gibwork-createbounty.md

WHAT IT DOES

What gibwork_createBounty does on Sap

AI agents use gibwork_createBounty to commit financial operations through Sap, usually the final step of a payment, billing, or trading workflow. A call moves real money.

Parameter	Type	Required	Description
`tags`	array	—	Tags parameter for Gibwork Create Bounty.
`title`	string	Yes	Bounty title
`creator`	string	Yes	Solana public key (base58)
`deadline`	number	—	Deadline (Unix timestamp)
`rewardMint`	string	—	Token mint address (base58)
`description`	string	Yes	Detailed bounty description
`rewardAmount`	string	Yes	Reward amount

Parameters from the server's own tool schema.

RISK

Why gibwork_createBounty is rated Critical

Creates on-chain financial escrow commitments, constituting a financial obligation with real funds.

From the tool's definition Create a new bounty on Gib Work with on-chain escrow

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gibwork_createBounty safely

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

gibwork_createBounty Approval-gated

Any call to gibwork_createBounty is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gibwork_createBounty": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sap, apply this rule, and every gibwork_createBounty call is checked against it from then on.

FAQ

Questions about gibwork_createBounty

What does the gibwork_createBounty tool do? +

Create a new bounty on Gib Work with on-chain escrow. SAP MCP context: Protocol gibwork; operation class write. Use for bounty creation, listing, and work submission. Confirm scope, payout, recipient, and deliverable evidence before writes. Use SAP attestation or feedback tools after work completion when reputation should be recorded on SAP. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial. It is categorised as a Financial tool in the Sap MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

What parameters does gibwork_createBounty accept? +

gibwork_createBounty accepts 7 parameters: tags, title, creator, deadline, rewardMint, description, rewardAmount. Required: title, creator, description, rewardAmount. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on gibwork_createBounty? +

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

What risk level is gibwork_createBounty? +

gibwork_createBounty is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit gibwork_createBounty? +

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

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

gibwork_createBounty is provided by the Sap MCP server (https://mcp.sap.oobeprotocol.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sap, and thousands of servers like it.

This server

All 375 Sap tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →