AI agents use feed_baseling to create or update resources in Baselings — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Baselings environment.
This tool modifies the state of a game entity (a baseling) by feeding it, which changes its hunger attribute and triggers a yield mechanism. It is a reversible state modification (Write) rather than destructive or financial, though it likely involves an on-chain transaction. The financial aspect is indirect (earning POOP token) rather than directly moving money, so Write is the most accurate category.
From the tool's definition Feed a baseling (increases hunger, earns POOP after 4hr delay)
Attacks that exploit this kind of access
Feed a baseling (increases hunger, earns POOP after 4hr delay). It is categorised as a Write tool in the Baselings MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Baselings MCP server in PolicyLayer and add a rule for feed_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.
feed_baseling is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the feed_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 feed_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.
feed_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 →