AI agents use create_session to create or update resources in Rize — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rize environment.
This tool creates a new time session record, which is a reversible write operation. While it modifies state in the Rize system, the action can be undone (sessions can be deleted or modified). It has medium severity because misuse could create spurious time entries affecting productivity analytics and billing/invoicing, but the impact is contained to the time tracking system and reversible.
From the tool's definition Tool name 'create_session' combined with description 'Create a new time session' indicates creation of a new data record in the time tracking system.
Attacks that exploit this kind of access
Create a new time session. It is categorised as a Write tool in the Rize MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rize MCP server in PolicyLayer and add a rule for create_session: 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.
create_session is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_session 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 create_session. 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.
create_session 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 →