List all Goatcounter sites accessible with the current API key.
AI agents call list_sites 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 returns a list of accessible sites. It performs a read-only operation that retrieves metadata about sites but does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal—an attacker gains visibility into what sites are monitored but cannot alter analytics data, delete sites, or trigger external operations.
From the tool's definition Tool name is 'list_sites' and description states it 'List[s] all Goatcounter sites accessible with the current API key' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all Goatcounter sites accessible with the current API key. 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 list_sites: 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.
list_sites 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 list_sites 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 list_sites. 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.
list_sites 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 →