AI agents call mft_flywheel 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 provides informational analysis of tokenomics rather than performing any transaction, state change, or financial action. It is purely educational/analytical in nature. While the server itself enables financial operations (USDC/ETH/BTC earning), this specific tool only reads and explains the MfT flywheel concept without executing trades, transfers, or irreversible changes.
From the tool's definition Tool name 'mft_flywheel' and description 'Understand the MfT tokenomics flywheel' indicate this is a read-only operation that retrieves or queries information about tokenomics mechanics.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Understand the MfT tokenomics flywheel — how every game action burns MfT supply. The key to understanding why MfT is the alpha. 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 mft_flywheel: 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.
mft_flywheel 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 mft_flywheel 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 mft_flywheel. 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.
mft_flywheel 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 →