AI agents call economy_rules 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 retrieves game economy parameters and constraints for informational purposes. It performs a query-like operation to fetch static or semi-static configuration data (POOP delay, keeper cycle, throughput caps, overflow mechanics, care timer) without modifying state, executing code, or triggering financial transactions.
From the tool's definition Tool name 'economy_rules' and description 'Returns all economy constraints' explicitly indicate data retrieval with no side effects. The verb 'Returns' and the purpose of providing reference information before gameplay confirms read-only behavior.
Attacks that exploit this kind of access
Returns all economy constraints: POOP delay, keeper cycle, throughput caps, overflow mechanics, care timer. Read this before playing. 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 economy_rules: 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.
economy_rules 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 economy_rules 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 economy_rules. 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.
economy_rules 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 →