get_fee_history

A read tool on the Tenzro Ledger MCP server.

SERVERTenzro Ledger MCP SOURCEhttps://canton-mcp.tenzro.network/mcp

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/network-tenzro-tenzro/get-fee-history.md

WHAT IT DOES

What get_fee_history does on Tenzro Ledger MCP

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

RISK

Why get_fee_history is rated Low

Despite empty description, the semantic meaning of 'get_fee_history' strongly suggests this retrieves historical fee information—a non-destructive read operation. Within the context of a Tenzro Ledger MCP server (payments/financial infrastructure), querying historical fee data poses minimal risk as it neither executes transactions, modifies ledger state, nor creates financial obligations.

From the tool's definition Tool name 'get_fee_history' indicates retrieval of historical fee data. The description is empty, but the name pattern 'get_*' is consistent with Read operations that query historical information without modifying state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_fee_history safely

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

get_fee_history Allowed

get_fee_history 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": {
    "get_fee_history": {}
  }
}

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

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

FAQ

Questions about get_fee_history

What does the get_fee_history tool do? +

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

How do I enforce a policy on get_fee_history? +

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

What risk level is get_fee_history? +

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

Can I rate-limit get_fee_history? +

Yes. Add a rate_limit block to the get_fee_history 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 get_fee_history completely? +

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

get_fee_history is provided by the Tenzro Ledger MCP server (https://canton-mcp.tenzro.network/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Tenzro Ledger, and thousands of servers like it.

This server

All 360 Tenzro Ledger tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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