estimate_gas_cost
AI agents call estimate_gas_cost to retrieve information from Blocknative without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool estimates gas costs, which is a computational query operation that retrieves market data without modifying blockchain state or executing transactions. However, confidence is slightly reduced because the description is empty. Severity is medium rather than low because gas cost estimates could influence financial decisions if misused in an automated context, though the tool itself only reads data.
From the tool's definition Tool name 'estimate_gas_cost' combined with server context (blocknative-mcp, sibling tools get_supported_chains and predict_gas_price) indicates this retrieves or queries blockchain gas price estimation data.
Attacks that exploit this kind of access
estimate_gas_cost. It is categorised as a Read tool in the Blocknative MCP Server, which means it retrieves data without modifying state.
Register the Blocknative MCP server in PolicyLayer and add a rule for estimate_gas_cost: 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 Blocknative. Nothing to install.
estimate_gas_cost 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 estimate_gas_cost 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 estimate_gas_cost. 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.
estimate_gas_cost is provided by the Blocknative MCP server (kukapay/blocknative-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 →