tenero_wallet_trades
Get trade history for a Stacks wallet address.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/tenero-wallet-trades.md
What tenero_wallet_trades does on Aibtc
AI agents call tenero_wallet_trades to retrieve information from Aibtc without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why tenero_wallet_trades is rated Low
This tool retrieves historical trade information associated with a wallet address on the Stacks blockchain. It queries existing data without creating, modifying, deleting, or executing any operations. The operation has no side effects and poses minimal risk—worst case, an attacker could enumerate wallet trade history if they know addresses, but this is typically public blockchain data.
From the tool's definition Tool name 'tenero_wallet_trades' and description 'Get trade history for a Stacks wallet address' indicate a retrieval operation without side effects. The verb 'Get' and the passive nature of querying historical data confirm this is a Read operation.
Attacks that exploit this kind of access
The rule that runs tenero_wallet_trades safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tenero_wallet_trades, this is the rule to start with:
tenero_wallet_trades is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every tenero_wallet_trades call is checked against it from then on.
Questions about tenero_wallet_trades
Get trade history for a Stacks wallet address. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.
Register the Aibtc MCP server in PolicyLayer and add a rule for tenero_wallet_trades: 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 Aibtc. Nothing to install.
tenero_wallet_trades 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 tenero_wallet_trades 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 tenero_wallet_trades. 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.
tenero_wallet_trades is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aibtc, and thousands of servers like it.
This server
Across the catalogue