bitflow_get_or_create_keeper_contract

WHAT IT DOES

What bitflow_get_or_create_keeper_contract does on Stacks AI MCP Server

AI agents use bitflow_get_or_create_keeper_contract to create or update resources in Stacks AI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Stacks AI MCP Server environment.

WHY IT NEEDS A POLICY

Why bitflow_get_or_create_keeper_contract needs a policy

The tool either retrieves an existing keeper contract (Read) or creates a new one (Write) for automated trading on a DeFi protocol. Creation of a keeper contract is a blockchain write operation that deploys or registers a contract enabling automated trading actions. Since the most severe applicable category when spanning multiple behaviors applies, this is Write.

From the tool's definition 'Get or create keeper contract for automated trading using official SDK'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bitflow_get_or_create_keeper_contract Rate-limited

bitflow_get_or_create_keeper_contract stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bitflow_get_or_create_keeper_contract": {
      "limits": [
        {
          "counter": "bitflow_get_or_create_keeper_contract_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Stacks AI MCP Server, so you can run agents against it safely.

FAQ

Questions about bitflow_get_or_create_keeper_contract

What does the bitflow_get_or_create_keeper_contract tool do? +

Get or create keeper contract for automated trading using official SDK. It is categorised as a Write tool in the Stacks AI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on bitflow_get_or_create_keeper_contract? +

Register the Stacks AI MCP Server MCP server in PolicyLayer and add a rule for bitflow_get_or_create_keeper_contract: 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.

What risk level is bitflow_get_or_create_keeper_contract? +

bitflow_get_or_create_keeper_contract is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit bitflow_get_or_create_keeper_contract? +

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

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

bitflow_get_or_create_keeper_contract 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.

// THE FULL RECORD

bitflow_get_or_create_keeper_contract is one line of Stacks AI MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →