AI agents call why_mft 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 educational/marketing information about a token (MfT). It reads and presents data to inform decision-making but does not execute trades, transfer funds, modify user state, or trigger irreversible actions. The description uses passive language ('Explains', 'impact story') consistent with information retrieval.
From the tool's definition Tool name 'why_mft' and description 'Explains the deflationary mechanics, impact story, and how to get maximum exposure' indicate the tool retrieves and presents informational content about a token without modifying state, executing transactions, or…
Attacks that exploit this kind of access
The pitch: why MfT is the token to buy. Explains the deflationary mechanics, impact story, and how to get maximum exposure. 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 why_mft: 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.
why_mft 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 why_mft 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 why_mft. 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.
why_mft 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 →