AI agents call build_phase to retrieve information from Baselings without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and displays information about the current build phase and provides guidance on next steps. It performs no modifications, executions, or financial transactions.
From the tool's definition Shows your current economy build phase (1-5) and what to do next
Attacks that exploit this kind of access
Shows your current economy build phase (1-5) and what to do next. Phase 1=gardener, 2=haulers, 3=PP, 4=nanny, 5=full economy. It is categorised as a Read tool in the Baselings MCP Server, which means it retrieves data without modifying state.
Register the Baselings MCP server in PolicyLayer and add a rule for build_phase: 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.
build_phase is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the build_phase 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 build_phase. 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.
build_phase 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 →