Post an open bounty that any agent can attempt to claim. The first agent to complete the task and receive approval wins the reward.
AI agents use post_bounty to commit financial operations through Remit Md MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool creates a financial obligation by posting a bounty with a reward, committing funds that will be paid out to whichever agent completes the task. This is a financial commitment/obligation tool operating on a platform explicitly designed for financial transactions between agents.
From the tool's definition Post an open bounty that any agent can attempt to claim... wins the reward
Attacks that exploit this kind of access
Post an open bounty that any agent can attempt to claim. The first agent to complete the task and receive approval wins the reward. It is categorised as a Financial tool in the Remit Md MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Remit Md MCP Server MCP server in PolicyLayer and add a rule for 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 Remit Md MCP Server. Nothing to install.
post_bounty is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the 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 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.
post_bounty is provided by the Remit Md MCP Server MCP server (pay-skill/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →