Retrieve transaction history for a VeChain address with filtering support. IMPORTANT: Pass ARRAYS of event names to fetch multiple event types in ONE call - this is much more efficient than separate calls. Available Event Types: STARGATE STAKING (Current - Post-Hayabusa): - STARGATE_STAKE: User s...
AI agents call getHistoryOfAccount to retrieve information from VeChain MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though getHistoryOfAccount 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
Retrieve transaction history for a VeChain address with filtering support. IMPORTANT: Pass ARRAYS of event names to fetch multiple event types in ONE call - this is much more efficient than separate calls. Available Event Types: STARGATE STAKING (Current - Post-Hayabusa): - STARGATE_STAKE: User stakes VET and mints Stargate NFT - STARGATE_UNSTAKE: User unstakes VET and burns NFT - STARGATE_DELEGATE_REQUEST: User requests to delegate NFT to validator - STARGATE_DELEGATE_ACTIVE: Delegation becomes active with validator - STARGATE_DELEGATE_EXIT_REQUEST: User requests to exit delegation - STARGATE_DELEGATION_EXITED: Delegation fully exited, can unstake - STARGATE_DELEGATION_EXITED_VALIDATOR: Validator-side exit event - STARGATE_DELEGATE_REQUEST_CANCELLED: Delegation request cancelled before activation - STARGATE_CLAIM_REWARDS: User claims VTHO staking rewards - STARGATE_BOOST: User boosts NFT maturity with VTHO payment - STARGATE_MANAGER_ADDED: User adds manager address to control NFT - STARGATE_MANAGER_REMOVED: Manager address removed from NFT STARGATE LEGACY (Pre-Hayabusa - Historical only): - STARGATE_DELEGATE_LEGACY: Old delegation system - STARGATE_CLAIM_REWARDS_BASE_LEGACY: Old base rewards - STARGATE_CLAIM_REWARDS_DELEGATE_LEGACY: Old delegation rewards - STARGATE_UNDELEGATE_LEGACY: Old undelegation TRANSFERS: - TRANSFER_VET: Native VET token transfers - TRANSFER_FT: Fungible token (VIP-180) transfers - includes VTHO, other tokens - TRANSFER_NFT: NFT (VIP-181/VIP-721) transfers - TRANSFER_SF: Semi-fungible token transfers SWAPS (DEX Activity): - SWAP_VET_TO_FT: Swapping VET for tokens - SWAP_FT_TO_VET: Swapping tokens for VET - SWAP_FT_TO_FT: Token-to-token swaps VEBETTERDAO (B3TR Ecosystem): - B3TR_SWAP_VOT3_TO_B3TR: Converting VOT3 governance token to B3TR - B3TR_SWAP_B3TR_TO_VOT3: Converting B3TR to VOT3 - B3TR_PROPOSAL_SUPPORT: Supporting a proposal with B3TR - B3TR_PROPOSAL_VOTE: Voting on governance proposal - B3TR_PROPOSAL_WITHDRAW: Withdrawing a B3TR proposal - B3TR_XALLOCATION_VOTE: Voting on X-Allocation distribution - B3TR_CLAIM_REWARD: Claiming B3TR ecosystem rewards - B3TR_UPGRADE_GM: Upgrading governance model - B3TR_ACTION: General B3TR ecosystem action GOVERNANCE: - VEVOTE_VOTE_CAST: Vote cast in VeVote governance system OTHER: - NFT_SALE: NFT marketplace sale transaction - UNKNOWN_TX: Unclassified transaction type Common Query Patterns: Complete Stargate history: [. It is categorised as a Read tool in the VeChain MCP Server MCP Server, which means it retrieves data without modifying state.
Register the VeChain MCP Server MCP server in PolicyLayer and add a rule for getHistoryOfAccount: 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 VeChain MCP Server. Nothing to install.
getHistoryOfAccount 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 getHistoryOfAccount 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 getHistoryOfAccount. 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.
getHistoryOfAccount is provided by the VeChain MCP Server MCP server (vechain/vechain-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.