AI agents call get_lottery_by_date_range to retrieve information from Lottery without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves historical lottery data within a specified date range. It performs a read-only operation on existing data with no capability to modify, delete, execute code, or affect financial systems. The retrieval of historical lottery information poses minimal security risk in the context of an AI agent's potential misuse.
From the tool's definition Tool name 'get_lottery_by_date_range' and description '按日期范围查询双色球开奖数据' (query double-color ball lottery data by date range) indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
按日期范围查询双色球开奖数据. It is categorised as a Read tool in the Lottery MCP Server, which means it retrieves data without modifying state.
Register the Lottery MCP server in PolicyLayer and add a rule for get_lottery_by_date_range: 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 Lottery. Nothing to install.
get_lottery_by_date_range 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 get_lottery_by_date_range 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 get_lottery_by_date_range. 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.
get_lottery_by_date_range is provided by the Lottery MCP server (lumosylva/lottery-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 →