List location statistics.
AI agents call get_stats_locations to retrieve information from Goatcounter MCP Server 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 analytics data about visitor locations. It performs read-only access to existing Goatcounter statistics with no capability to modify, delete, or execute external operations. The blast radius of misuse is minimal—an agent could only exfiltrate analytics insights that are typically semi-public on a website owner's account.
From the tool's definition Tool retrieves location statistics from web analytics data. The description indicates it 'List location statistics' and the server is designed to 'query Goatcounter web analytics data' without modification.
Attacks that exploit this kind of access
List location statistics. It is categorised as a Read tool in the Goatcounter MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Goatcounter MCP Server MCP server in PolicyLayer and add a rule for get_stats_locations: 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 Goatcounter MCP Server. Nothing to install.
get_stats_locations 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_stats_locations 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_stats_locations. 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_stats_locations is provided by the Goatcounter MCP Server MCP server (rafaljanicki/goatcounter-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 →