Get user information with keeper contracts and orders using official SDK
AI agents call bitflow_get_keeper_user to retrieve information from Stacks AI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user information and associated keeper contracts/orders. It performs no state changes, executes no code, deletes nothing, and involves no financial transactions. It is purely informational in nature, making it a Read category tool with low severity since misuse would only expose data without causing operational harm.
From the tool's definition Tool name 'bitflow_get_keeper_user' with description 'Get user information with keeper contracts and orders using official SDK' indicates a query/retrieval operation.
Attacks that exploit this kind of access
Get user information with keeper contracts and orders 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_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 Stacks AI MCP Server. Nothing to install.
bitflow_get_keeper_user 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_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.
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.
bitflow_get_keeper_user 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →