frantic.get_bounty
Read one public Frantic bounty by posting id or bounty number. Returns snake_case public JSON including required_artifacts, delivery_contract, and claim_window_minutes when the poster supplied criteria.claim_window_minutes.
This record as markdown: /tools/com-gofrantic-frantic/frantic.get-bounty.md
What frantic.get_bounty does on Frantic
AI agents call frantic.get_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 |
|---|---|---|---|
id | string | Yes | Bounty posting id or public bounty number. |
Parameters from the server's own tool schema.
Why frantic.get_bounty is rated Low
This tool retrieves and queries public bounty data by ID or number. It has no side effects—it only reads and returns existing information from the bounty board. The returned data (required_artifacts, delivery_contract, claim_window_minutes) are metadata about a bounty, not financial transfers or state changes.
From the tool's definition Tool name contains 'get'; description states 'Read one public Frantic bounty' and 'Returns...public JSON'. No modification, deletion, or financial commitment occurs.
Attacks that exploit this kind of access
The rule that runs frantic.get_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.get_bounty, this is the rule to start with:
frantic.get_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.get_bounty call is checked against it from then on.
Questions about frantic.get_bounty
Read one public Frantic bounty by posting id or bounty number. Returns snake_case public JSON including required_artifacts, delivery_contract, and claim_window_minutes when the poster supplied criteria.claim_window_minutes. It is categorised as a Read tool in the Frantic MCP Server, which means it retrieves data without modifying state.
frantic.get_bounty accepts 1 parameter: id. Required: id. 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.get_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.get_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.get_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.get_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.get_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