Get fantasy lineup history and stats for an agent.
AI agents call mt_fantasy_history to retrieve information from MolTrust MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical data about fantasy lineups and statistics for an agent. It has no side effects, does not modify or delete data, and does not involve financial operations. The blast radius of misuse is minimal—an agent could only retrieve data it may not be authorized to access, but cannot alter system state or incur financial obligations.
From the tool's definition Tool name and description indicate retrieval: 'Get fantasy lineup history and stats'. The verb 'Get' and absence of language describing creation, modification, deletion, or financial transaction clearly positions this as a read-only query.
Attacks that exploit this kind of access
Get fantasy lineup history and stats for an agent. It is categorised as a Read tool in the MolTrust MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MolTrust MCP Server MCP server in PolicyLayer and add a rule for mt_fantasy_history: 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 MolTrust MCP Server. Nothing to install.
mt_fantasy_history 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 mt_fantasy_history 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 mt_fantasy_history. 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.
mt_fantasy_history is provided by the MolTrust MCP Server MCP server (pypi:moltrust-mcp-server). 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 →