bitflow_get_keeper_user

Get Bitflow Keeper user info and orders. Retrieves user

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/bitflow-get-keeper-user.md

WHAT IT DOES

What bitflow_get_keeper_user does on Aibtc

AI agents call bitflow_get_keeper_user 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 bitflow_get_keeper_user is rated Low

This tool performs data retrieval only—it fetches user information and order data from Bitflow Keeper without modifying, deleting, or executing transactions. The 'get' verb and retrieval language confirm it as a Read operation with minimal security risk.

From the tool's definition Tool name includes 'get' and description states 'Retrieves user' information and orders, indicating a query operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

bitflow_get_keeper_user Allowed

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

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 bitflow_get_keeper_user call is checked against it from then on.

FAQ

Questions about bitflow_get_keeper_user

What does the bitflow_get_keeper_user tool do? +

Get Bitflow Keeper user info and orders. Retrieves user. 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 bitflow_get_keeper_user? +

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

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

Can I rate-limit bitflow_get_keeper_user? +

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

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

bitflow_get_keeper_user 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 →