Get information about the current Goatcounter user and API key.
AI agents call get_me 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 retrieves information about the authenticated user and their API key credentials. It performs no side effects, creates no data, executes no commands, and deletes nothing. While exposing API key information could be sensitive in certain contexts, the tool itself is fundamentally a read operation.
From the tool's definition Tool name 'get_me' and description 'Get information about the current Goatcounter user and API key' indicate a read-only retrieval operation that queries user metadata without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
Get information about the current Goatcounter user and 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 get_me: 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_me 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_me 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_me. 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_me 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 →