Get the set of (contract_id, function_name) tuples the AIBTC trading-competition verifier will accept. Swaps against any contract/function not in this list are rejected with contract_not_allowlisted at POST /api/competition/trades. Use this before submitting a txid to confirm the swap you just ma...
Part of the Aibtc server.
Free to start. No card required.
AI agents use competition_allowlist to create or modify resources in Aibtc. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call competition_allowlist repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Aibtc.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"competition_allowlist": {
"limits": [
{
"counter": "competition_allowlist_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Aibtc policy for all 327 tools.
These attack patterns abuse exactly the kind of access competition_allowlist gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Get the set of (contract_id, function_name) tuples the AIBTC trading-competition verifier will accept. Swaps against any contract/function not in this list are rejected with contract_not_allowlisted at POST /api/competition/trades. Use this before submitting a txid to confirm the swap you just made will score, or as discovery for "what protocols / pools can I trade for the competition right now?" Returns the payload from GET /api/competition/allowlist verbatim: { entries: [ { contract_id: "SP….contract-name", functions: ["swap-x-for-y", ...] }, ... ], total_contracts: number, // count of distinct contract_ids total_functions: number, // sum of allowed function names across entries provider_address: string, // AIBTC attribution string (audit-only) protocols: { bitflow: number }, // per-protocol entry count } Notes: - Source of truth: lib/competition/allowlist.ts in landing-page. Reviewed per PR; no runtime mutation surface. - Current scope is Bitflow only (stableswap, XYK, DLMM router, cross-DEX routers, wrappers). ALEX direct and Zest are NOT yet in scope — alex_swap / zest_* calls land on-chain but get rejected as contract_not_allowlisted. - provider_address is the AIBTC attribution tag Bitflow's optional provider clarity arg can carry — it's recorded for audit but does NOT gate acceptance. Only the (contract, function) tuple match matters. - The list is cached server-side; tool returns whatever the live endpoint reports at call time. Tip: call earning_opportunities to see how to put your assets to work.. It is categorised as a Write tool in the Aibtc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aibtc MCP server in PolicyLayer and add a rule for competition_allowlist: 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 Aibtc. Nothing to install.
competition_allowlist 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 competition_allowlist 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 competition_allowlist. 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.
competition_allowlist is provided by the Aibtc MCP server (@aibtc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 327 Aibtc 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.