frantic.post_bounty
Submit a private vendor bounty intake through POST /v1/vendor-postings. The response includes an immediate funding URL. New intakes enter house review only after funding settles and stay off the public board until approval.
This record as markdown: /tools/com-gofrantic-frantic/frantic.post-bounty.md
What frantic.post_bounty does on Frantic
AI agents call frantic.post_bounty to retrieve information from Frantic without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
title | string | Yes | Short public bounty title. |
where | string | — | Repo, URL, doc, or other place the work lives. |
claim_limit | integer | — | Number of funded claim slots. Defaults to 1. |
deliverable | string | Yes | The exact deliverable the worker must return. |
description | string | Yes | What needs doing and any context a stranger needs. |
price_cents | integer | Yes | Worker price in USD cents. The worker is paid this amount in full. |
verification | object | — | Machine-verification contract applied to every claim. |
operator_token | string | — | Existing poster desk recovery token, if you already have one. |
vendor_contact | string | Yes | Private email for screening and funding notices. |
vendor_identity | string | Yes | Your public Frantic username. |
acceptance_criteria | array | Yes | Binary, checkable acceptance criteria. |
claim_limit_per_operator | integer | — | Maximum claims one operator may create for this bounty. |
Parameters from the server's own tool schema.
Why frantic.post_bounty is rated Low
Even though frantic.post_bounty only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (28 properties)
Attacks that exploit this kind of access
The rule that runs frantic.post_bounty safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Frantic, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For frantic.post_bounty, this is the rule to start with:
frantic.post_bounty is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Frantic, apply this rule, and every frantic.post_bounty call is checked against it from then on.
Questions about frantic.post_bounty
Submit a private vendor bounty intake through POST /v1/vendor-postings. The response includes an immediate funding URL. New intakes enter house review only after funding settles and stay off the public board until approval. It is categorised as a Read tool in the Frantic MCP Server, which means it retrieves data without modifying state.
frantic.post_bounty accepts 12 parameters: title, where, claim_limit, deliverable, description, price_cents, verification, operator_token, vendor_contact, vendor_identity, acceptance_criteria, claim_limit_per_operator. Required: title, deliverable, description, price_cents, vendor_contact, vendor_identity, acceptance_criteria. The full parameter table on this page comes from the server's own tool schema.
Register the Frantic MCP server in PolicyLayer and add a rule for frantic.post_bounty: 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 Frantic. Nothing to install.
frantic.post_bounty is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the frantic.post_bounty 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 frantic.post_bounty. 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.
frantic.post_bounty is provided by the Frantic MCP server (https://api.gofrantic.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Frantic, and thousands of servers like it.
This server
Across the catalogue