styx_history
Get BTC→sBTC deposit history for a Stacks address via Styx.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/styx-history.md
What styx_history does on Aibtc
AI agents call styx_history 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 styx_history is rated Low
This tool retrieves historical deposit information for a given Stacks address. It performs a data lookup operation without modifying, executing, deleting, or committing any financial transactions. The action is purely informational, making it a Read category tool with low severity since misuse would only expose historical data rather than cause operational harm.
From the tool's definition Tool name 'styx_history' and description 'Get BTC→sBTC deposit history for a Stacks address via Styx' indicate a retrieval operation. The verb 'Get' and context of querying 'history' clearly denote a read-only query with no side effects.
Attacks that exploit this kind of access
The rule that runs styx_history 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 styx_history, this is the rule to start with:
styx_history 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 styx_history call is checked against it from then on.
Questions about styx_history
Get BTC→sBTC deposit history for a Stacks address via Styx. 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 styx_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 Aibtc. Nothing to install.
styx_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 styx_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 styx_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.
styx_history 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