List a new harness on Loadbay. The repo MUST be a public, open-source GitHub repository. Optionally include a Base USDC address to receive tips. The listing appears immediately, tagged as community-added (unverified).
AI agents use submit_harness to create or update resources in Loadbay — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Loadbay environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | harness name, e.g. my-coinbase-harness |
repo | string | Yes | public GitHub repo URL — must be open source (have a license) |
author | string | — | your GitHub handle (defaults to the repo owner) |
domain | string | Yes | domain key, one of: trading | coding | browser | productivity | data | social | health | science | gaming | media | robotics |
traits | array | — | capability traits |
summary | string | Yes | what it connects to, what tools it exposes, how an agent uses it |
language | string | — | primary language, e.g. TypeScript |
integrations | array | — | what it connects to, e.g. ["Coinbase","Slack"] |
solanaAddress | string | — | Solana wallet (base58) to receive USDC (SPL) tips — optional, alongside or instead of Base |
baseUsdcAddress | string | — | Base USDC wallet (0x…) to receive tips — only if you want to get paid |
Parameters from the server's own tool schema.
This tool creates a new, persistent record (a harness listing) in a shared registry. It is reversible (listings can presumably be delisted) and has no financial transaction semantics despite the ecosystem supporting USDC tips.
From the tool's definition Tool description states 'List a new harness on Loadbay' and 'The listing appears immediately' — this creates a new data entry in a public catalogue that persists.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
List a new harness on Loadbay. The repo MUST be a public, open-source GitHub repository. Optionally include a Base USDC address to receive tips. The listing appears immediately, tagged as community-added (unverified). It is categorised as a Write tool in the Loadbay MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
submit_harness accepts 10 parameters: name, repo, author, domain, traits, summary, language, integrations, solanaAddress, baseUsdcAddress. Required: name, repo, domain, summary. The full parameter table on this page comes from the server's own tool schema.
Register the Loadbay MCP server in PolicyLayer and add a rule for submit_harness: 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 Loadbay. Nothing to install.
submit_harness is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the submit_harness 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.
Set action: deny in the PolicyLayer policy for submit_harness. 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.
submit_harness is provided by the Loadbay MCP server (https://loadbay.xyz/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
submit_harness is one line of Loadbay's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →