AI agents call rybbit_get_overview to retrieve information from Rybbit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries analytics data without side effects. It supports filtering and date ranges but only performs read operations on existing metrics. No data is created, modified, deleted, or used to trigger external operations. The low severity reflects minimal blast radius—an AI agent misusing this tool would only access unwanted analytics visibility, not cause damage or data loss.
From the tool's definition Tool name contains 'get_' prefix and description states 'Get aggregated overview metrics' with retrieval operations: sessions, pageviews, unique users, etc. No modification, deletion, or execution capability mentioned.
Attacks that exploit this kind of access
Get aggregated overview metrics for a site: sessions, pageviews, unique users, pages per session, bounce rate, and average session duration. Supports date range and filters. It is categorised as a Read tool in the Rybbit MCP Server, which means it retrieves data without modifying state.
Register the Rybbit MCP server in PolicyLayer and add a rule for rybbit_get_overview: 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 Rybbit. Nothing to install.
rybbit_get_overview 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 rybbit_get_overview 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 rybbit_get_overview. 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.
rybbit_get_overview is provided by the Rybbit MCP server (nks-hub/rybbit-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 →