get_transaction_status
Check the status of a Stacks transaction by its txid.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/get-transaction-status.md
What get_transaction_status does on Aibtc
AI agents call get_transaction_status 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 get_transaction_status is rated Low
This tool performs a read-only query against a blockchain (Stacks) to fetch transaction status. It has no side effects, no code execution capability, and no ability to modify or delete data. The blast radius of misuse is minimal — an attacker could only view transaction statuses they already have transaction IDs for, which provides no confidentiality risk beyond normal blockchain transparency.
From the tool's definition Tool description states 'Check the status of a Stacks transaction by its txid' — a query operation that retrieves transaction status information without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
The rule that runs get_transaction_status 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_transaction_status, this is the rule to start with:
get_transaction_status 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 get_transaction_status call is checked against it from then on.
Questions about get_transaction_status
Check the status of a Stacks transaction by its txid. 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 get_transaction_status: 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.
get_transaction_status 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_transaction_status 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_transaction_status. 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_transaction_status 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