AI agents use resurrect_baseling to commit financial operations through Baselings — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool operates within a blockchain-based game where actions translate to on-chain transactions involving real assets (USDC, ETH, BTC). Resurrecting a baseling almost certainly requires spending tokens or paying fees on-chain, making it a financial action. The sibling tools (buy_egg, buy_food, buy_house) confirm that purchases are a core mechanic, and resurrection follows the same pattern.
From the tool's definition 'Revive a dead baseling' in a 'yield-generating pet game' that 'Enables agents to manage workers, claim yields, and execute strategies to earn USDC, ETH, or BTC' — resurrection likely costs in-game currency or on-chain tokens, constituting a financial…
Attacks that exploit this kind of access
Revive a dead baseling (needs 10 feeds after). It is categorised as a Financial tool in the Baselings MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Baselings MCP server in PolicyLayer and add a rule for resurrect_baseling: 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 Baselings. Nothing to install.
resurrect_baseling is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the resurrect_baseling 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 resurrect_baseling. 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.
resurrect_baseling is provided by the Baselings MCP server (jimbo530/baselings-mcp). 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 →