Query raw click records via POST /clicks/log. Returns individual click
AI agents call keitaro_get_clicks to retrieve information from Keitaro MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is fundamentally a Read operation—it queries and retrieves click records from a tracking database. However, the severity is elevated to 'medium' rather than 'low' because click logs typically contain sensitive information (user IPs, timestamps, referral sources, potentially personally identifiable details) that could be abused for privacy violations or competitive intelligence if accessed by a compromised agent.
From the tool's definition Tool name 'keitaro_get_clicks' and description 'Query raw click records' and 'Returns individual click' indicate retrieval of data without modification.
Attacks that exploit this kind of access
Query raw click records via POST /clicks/log. Returns individual click. It is categorised as a Read tool in the Keitaro MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Keitaro MCP Server MCP server in PolicyLayer and add a rule for keitaro_get_clicks: 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 Keitaro MCP Server. Nothing to install.
keitaro_get_clicks 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 keitaro_get_clicks 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 keitaro_get_clicks. 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.
keitaro_get_clicks is provided by the Keitaro MCP Server MCP server (keitaromanager/keitaro-mcp). 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 →