get_account_transactions

Get transaction history for an account.

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/get-account-transactions.md

WHAT IT DOES

What get_account_transactions does on Aibtc

AI agents call get_account_transactions 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.

RISK

Why get_account_transactions is rated Low

This tool queries and retrieves historical transaction data without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with minimal security risk—the main concern would be unauthorized access to sensitive account history, but the tool itself performs no side effects.

From the tool's definition Tool name 'get_account_transactions' and description 'Get transaction history for an account' indicate a retrieval operation with no modification of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_account_transactions 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 get_account_transactions, this is the rule to start with:

get_account_transactions Allowed

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

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

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

FAQ

Questions about get_account_transactions

What does the get_account_transactions tool do? +

Get transaction history for an account. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_account_transactions? +

Register the Aibtc MCP server in PolicyLayer and add a rule for get_account_transactions: 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.

What risk level is get_account_transactions? +

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

Can I rate-limit get_account_transactions? +

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

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

get_account_transactions 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.

KEEP EXPLORING

More on Aibtc, and thousands of servers like it.

This server

All 358 Aibtc 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 →