AI agents use assign_worker 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 creates or modifies data (baseling worker assignment) without permanently destroying it or executing arbitrary code. The assignment appears reversible (a baseling can be reassigned), making it a Write action rather than Destructive or Execute. The severity is medium because misuse could disrupt game strategy and resource accumulation, but the effects are contained within the game and reversible.
From the tool's definition Tool description states 'Put a baseling to work' which modifies the state of a baseling by assigning it to a role (garden, pp, nanny, or hauler). This is a reversible state change operation.
Attacks that exploit this kind of access
Put a baseling to work (garden, pp, nanny, or hauler). 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 assign_worker: 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.
assign_worker 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 assign_worker 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 assign_worker. 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.
assign_worker 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 →