bitflow_get_keeper_tokens
Get available tokens for keeper operations using official SDK
This record as markdown: /tools/stack-ai-mcp-stacks-mcp-server/bitflow-get-keeper-tokens.md
What bitflow_get_keeper_tokens does on Stacks AI MCP Server
AI agents call bitflow_get_keeper_tokens to retrieve information from Stacks AI MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why bitflow_get_keeper_tokens is rated Low
The tool retrieves information about available tokens for keeper operations. The verb 'get' combined with the read-only nature of querying token availability (no creation, modification, deletion, or execution of transactions) classifies this as a Read operation. Low severity reflects that querying token data has no blast radius—it cannot cause financial loss, execute trades, or modify state.
From the tool's definition Tool name contains 'get' and description states 'Get available tokens' with no mention of state modification, deletion, or side effects. This is a retrieval operation using the official SDK.
Attacks that exploit this kind of access
The rule that runs bitflow_get_keeper_tokens safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stacks AI MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bitflow_get_keeper_tokens, this is the rule to start with:
bitflow_get_keeper_tokens 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 Stacks AI MCP Server, apply this rule, and every bitflow_get_keeper_tokens call is checked against it from then on.
Questions about bitflow_get_keeper_tokens
Get available tokens for keeper operations using official SDK. It is categorised as a Read tool in the Stacks AI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Stacks AI MCP Server MCP server in PolicyLayer and add a rule for bitflow_get_keeper_tokens: 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 Stacks AI MCP Server. Nothing to install.
bitflow_get_keeper_tokens 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 bitflow_get_keeper_tokens 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 bitflow_get_keeper_tokens. 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.
bitflow_get_keeper_tokens is provided by the Stacks AI MCP Server MCP server (stack-ai-mcp/stacks-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stacks AI MCP Server, and thousands of servers like it.
This server
Across the catalogue