Withdraw your pending bid on an offer. Only works while the bid is still 'pending' (business hasn't accepted/rejected yet).
Part of the Computeback server.
Free to start. No card required.
AI agents use withdraw_bid to initiate financial transactions through Computeback. Financial operations involve real money and are irreversible once processed. PolicyLayer blocks financial tools by default, requiring explicit human approval with transaction-level limits to prevent unauthorised spending.
withdraw_bid moves real money. Without a policy, an autonomous agent could initiate transactions that drain accounts or exceed budgets. PolicyLayer blocks financial tools by default, requiring human-in-the-loop approval with configurable spending limits per transaction and per time window.
Financial tools involve real money. Block by default and require explicit human approval before enabling.
{
"version": "1",
"default": "deny",
"tools": {
"withdraw_bid": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
}See the full Computeback policy for all 28 tools.
These attack patterns abuse exactly the kind of access withdraw_bid gives an agent. Each links to the full case and the policy that stops it:
Other financial tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Withdraw your pending bid on an offer. Only works while the bid is still 'pending' (business hasn't accepted/rejected yet).. It is categorised as a Financial tool in the Computeback MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Computeback MCP server in PolicyLayer and add a rule for withdraw_bid: 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 Computeback. Nothing to install.
withdraw_bid 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 withdraw_bid 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 withdraw_bid. 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.
withdraw_bid is provided by the Computeback MCP server (@autonomad1/computeback-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 28 Computeback tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.