Submit proof of completion for a claimed bounty. Only the claimant can call this.
AI agents use submit_bounty to create or update resources in Inkwell MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Inkwell MCP Server environment.
This tool submits proof/data associated with a bounty claim, which is a write operation (creating/updating a record). While bounties may involve financial payouts, this tool specifically submits proof of completion rather than directly moving money or committing financial obligations — the actual financial settlement would occur downstream.
From the tool's definition Submit proof of completion for a claimed bounty. Only the claimant can call this.
Attacks that exploit this kind of access
Submit proof of completion for a claimed bounty. Only the claimant can call this. It is categorised as a Write tool in the Inkwell MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Inkwell MCP Server MCP server in PolicyLayer and add a rule for submit_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 Inkwell MCP Server. Nothing to install.
submit_bounty 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_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 submit_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.
submit_bounty is provided by the Inkwell MCP Server MCP server (mumega-com/inkwell). 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 →