gibwork_submitWork

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

Medium RISK CLASS

Category Write

Parameters 43 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What gibwork_submitWork does on Sap

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

Parameter	Type	Required	Description
`notes`	string	—	Notes parameter for Gibwork Submit Work.
`wallet`	string	Yes	Solana public key (base58)
`bountyId`	string	Yes	Bounty ID parameter for Gibwork Submit Work.
`submissionUrl`	string	Yes	URL to the completed work (PR, doc, etc.)

Parameters from the server's own tool schema.

RISK

Why gibwork_submitWork is rated Medium

Creates or modifies bounty work submission records reversibly; financial context but tool itself writes data.

From the tool's definition Submit completed work for bounty; operation class write; payout, recipient confirmation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gibwork_submitWork 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_submitWork, this is the rule to start with:

gibwork_submitWork Rate-limited

gibwork_submitWork 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": {
    "gibwork_submitWork": {
      "limits": [
        {
          "counter": "gibwork_submitwork_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about gibwork_submitWork

What does the gibwork_submitWork tool do? +

Submit completed work for a Gib Work bounty. 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 Write tool in the Sap MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does gibwork_submitWork accept? +

gibwork_submitWork accepts 4 parameters: notes, wallet, bountyId, submissionUrl. Required: wallet, bountyId, submissionUrl. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on gibwork_submitWork? +

Register the Sap MCP server in PolicyLayer and add a rule for gibwork_submitWork: 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_submitWork? +

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

Can I rate-limit gibwork_submitWork? +

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

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

gibwork_submitWork 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 →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →