get_fee_history
AI agents call get_fee_history to retrieve information from Tenzro Ledger MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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
get_fee_history. It is categorised as a Read tool in the Tenzro Ledger MCP MCP Server, which means it retrieves data without modifying state.
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.
get_fee_history 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 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.
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.
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.
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 →