AI agents call rybbit_get_user_session_count 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 only queries and retrieves historical analytics data (session counts) without modifying, deleting, or executing operations. It has no side effects and is purely informational. The blast radius of misuse is minimal—an agent could only retrieve potentially sensitive user session data, but cannot alter or delete information.
From the tool's definition Tool description states it 'Get[s] the per-day session count' with no mention of modifications, deletions, or side effects. It is explicitly a retrieval function ('get') for analytics data.
Attacks that exploit this kind of access
Get the per-day session count for a single user across the requested time range. Useful for plotting user engagement intensity (calendar heatmap or sparkline). 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_user_session_count: 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_user_session_count 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_user_session_count 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_user_session_count. 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_user_session_count 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 →