This record as markdown: /tools/creativelead-unclick/lott-results.md
What lott_results does on UnClick
AI agents call lott_results to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
game | string | — | e.g. TattsLotto, Powerball |
draw_number | number | — |
Parameters from the server's own tool schema.
Why lott_results is rated Low
This tool retrieves public lottery results data from a service (The Lott). It performs a query-like operation with no capability to modify data, execute code, delete information, or affect financial transactions. The action is purely informational retrieval, fitting the Read category. Severity is low because misuse cannot cause damage—an agent querying lottery results poses no security risk.
From the tool's definition Tool name 'lott_results' and description 'Get Australian lottery results from The Lott' indicate retrieval of historical/current lottery data with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs lott_results safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For lott_results, this is the rule to start with:
lott_results is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every lott_results call is checked against it from then on.
Questions about lott_results
Get Australian lottery results from The Lott. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
lott_results accepts 2 parameters: game, draw_number. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for lott_results: 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 UnClick. Nothing to install.
lott_results 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 lott_results 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 lott_results. 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.
lott_results is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue