getFeeData

A read tool on the MCP Ethers Wallet MCP server.

SERVERMCP Ethers Wallet SOURCEcrazyrabbitltc/mcp-ethers-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/crazyrabbitltc-mcp-ethers-server/getfeedata.md

WHAT IT DOES

What getFeeData does on MCP Ethers Wallet

AI agents call getFeeData to retrieve information from MCP Ethers Wallet without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why getFeeData is rated Low

The tool name 'getFeeData' indicates retrieval of blockchain fee information, which is a read operation with no side effects. However, within the context of an Ethereum wallet server where an LLM could use this data to make transaction decisions, severity is rated medium rather than low—an attacker could use fee data queries to enumerate blockchain state or inform transaction timing attacks.

From the tool's definition Tool name 'getFeeData' with no description provided. Given the server context (Ethereum wallet interaction), this most likely retrieves gas fee or transaction cost data from the blockchain.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs getFeeData safely

PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Ethers Wallet, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getFeeData, this is the rule to start with:

getFeeData Allowed

getFeeData is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "getFeeData": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect MCP Ethers Wallet, apply this rule, and every getFeeData call is checked against it from then on.

FAQ

Questions about getFeeData

What does the getFeeData tool do? +

getFeeData is a read tool on the MCP Ethers Wallet MCP server. It is categorised as a Read tool in the MCP Ethers Wallet MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getFeeData? +

Register the MCP Ethers Wallet MCP server in PolicyLayer and add a rule for getFeeData: 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 MCP Ethers Wallet. Nothing to install.

What risk level is getFeeData? +

getFeeData is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit getFeeData? +

Yes. Add a rate_limit block to the getFeeData 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.

How do I block getFeeData completely? +

Set action: deny in the PolicyLayer policy for getFeeData. 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.

What MCP server provides getFeeData? +

getFeeData is provided by the MCP Ethers Wallet MCP server (crazyrabbitltc/mcp-ethers-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on MCP Ethers Wallet, and thousands of servers like it.

This server

All 69 MCP Ethers Wallet tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →