This record as markdown: /tools/io-github-1lystore-mcp-server/1ly-get-stats.md
What 1ly_get_stats does on 1ly
AI agents call 1ly_get_stats to retrieve information from 1ly without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why 1ly_get_stats is rated Low
This tool retrieves statistical information about a store or link. It performs no modifications, deletions, financial transactions, or external code execution. The requirement for an API key is a standard authentication control, not an elevation of risk category. The blast radius of misuse is limited to unauthorized access to statistics, which constitutes information disclosure but no operational or financial harm.
From the tool's definition Tool name '1ly_get_stats' and description 'Get store or link stats' indicate a retrieval operation with no side effects. The word 'Get' and 'stats' confirm this is a query/fetch action.
Attacks that exploit this kind of access
The rule that runs 1ly_get_stats safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 1ly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For 1ly_get_stats, this is the rule to start with:
1ly_get_stats 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 1ly, apply this rule, and every 1ly_get_stats call is checked against it from then on.
Questions about 1ly_get_stats
Get store or link stats (requires ONELY_API_KEY). It is categorised as a Read tool in the 1ly MCP Server, which means it retrieves data without modifying state.
Register the 1ly MCP server in PolicyLayer and add a rule for 1ly_get_stats: 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 1ly. Nothing to install.
1ly_get_stats 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 1ly_get_stats 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 1ly_get_stats. 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.
1ly_get_stats is provided by the 1ly MCP server (@1ly/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 1ly, and thousands of servers like it.
This server
Across the catalogue