Split a pair into two separate hands (when dealt two cards of the same value)
AI agents invoke blackjack-split to trigger actions in Blackjack MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers a game action within the blackjack session — splitting a hand into two — which changes the game state. It is an interactive operation with side effects on the game state, making it Execute. There are no real financial transactions, no data destruction, and no system-level code execution. Blast radius is minimal as it only affects an in-game state.
From the tool's definition Split a pair into two separate hands (when dealt two cards of the same value)
Documented attack patterns abuse exactly the kind of access blackjack-split gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Blackjack MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for blackjack-split:
{
"version": "1",
"default": "deny",
"tools": {
"blackjack-split": {
"limits": [
{
"counter": "blackjack-split_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}blackjack-split stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Split a pair into two separate hands (when dealt two cards of the same value). It is categorised as a Execute tool in the Blackjack MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Blackjack MCP Server MCP server in PolicyLayer and add a rule for blackjack-split: 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 Blackjack MCP Server. Nothing to install.
blackjack-split is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the blackjack-split 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 blackjack-split. 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.
blackjack-split is provided by the Blackjack MCP Server MCP server (nanobot-ai/blackjack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Blackjack MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Blackjack MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.