util_bridge_cost_budget
Sum gas + bridge fee + slippage budget into total cost
This record as markdown: /tools/io-github-davidmosiah-delx-protocol/util-bridge-cost-budget.md
What util_bridge_cost_budget does on Delx Protocol — Agent Recovery & Continuity
AI agents call util_bridge_cost_budget to retrieve information from Delx Protocol — Agent Recovery & Continuity 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 |
|---|---|---|---|
gas_usd | number | Yes | Estimated gas cost in USD |
slippage_usd | number | Yes | Slippage budget in USD |
bridge_fee_usd | number | Yes | Bridge fee in USD |
Parameters from the server's own tool schema.
Why util_bridge_cost_budget is rated Low
Even though util_bridge_cost_budget only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs util_bridge_cost_budget safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Protocol — Agent Recovery & Continuity, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For util_bridge_cost_budget, this is the rule to start with:
util_bridge_cost_budget 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 Delx Protocol — Agent Recovery & Continuity, apply this rule, and every util_bridge_cost_budget call is checked against it from then on.
Questions about util_bridge_cost_budget
Sum gas + bridge fee + slippage budget into total cost. It is categorised as a Read tool in the Delx Protocol — Agent Recovery & Continuity MCP Server, which means it retrieves data without modifying state.
util_bridge_cost_budget accepts 3 parameters: gas_usd, slippage_usd, bridge_fee_usd. Required: gas_usd, slippage_usd, bridge_fee_usd. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Protocol — Agent Recovery & Continuity MCP server in PolicyLayer and add a rule for util_bridge_cost_budget: 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 Delx Protocol — Agent Recovery & Continuity. Nothing to install.
util_bridge_cost_budget 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 util_bridge_cost_budget 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 util_bridge_cost_budget. 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.
util_bridge_cost_budget is provided by the Delx Protocol — Agent Recovery & Continuity MCP server (https://api.delx.ai/v1/mcp?src=registry). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Protocol — Agent Recovery & Continuity, and thousands of servers like it.
Across the catalogue