AI agents call get_sessions to retrieve information from Rize without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves session data filtered by time range. It performs no creation, modification, deletion, or execution of external commands. It is a straightforward read operation that retrieves information from the Rize time tracking system.
From the tool's definition Tool name 'get_sessions' and description 'Get sessions within a time range' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get sessions within a time range. It is categorised as a Read tool in the Rize MCP Server, which means it retrieves data without modifying state.
Register the Rize MCP server in PolicyLayer and add a rule for get_sessions: 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 Rize. Nothing to install.
get_sessions 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_sessions 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_sessions. 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_sessions is provided by the Rize MCP server (rize-io/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 →