// SCAN REPORT

Rize

28 tools. 13 can modify or destroy data without limits.

3 destructive tools with no built-in limits. Policy required.

Last updated: 3 Jul 2026

13 can modify or destroy data

15 read-only

28 tools total

Community server · catalogue entry verified 03/07/2026

How to control Rize ↓

TOOL MAP

What Rize exposes to your agents

Read (15) Write / Execute (10) Destructive / Financial (3)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Rize tools

Destructive · High delete_client Deleting a client is a destructive operation that cannot be undone and will likely cascade to associated projects, tasks, and time entries. Destructive · High delete_project The tool performs an irreversible deletion of a project, which cannot be undone. Destructive · High delete_task This tool permanently removes task records, which cannot be undone. Execute · Medium start_session_timer This tool executes a command to initiate a session timer in the Rize time-tracking system.

13 of Rize's 28 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Rize

PolicyLayer is an MCP gateway — it sits between your AI agents and Rize, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_client": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "create_client": {
    "limits": [
      {
        "counter": "create_client_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_apps_and_websites": {
    "limits": [
      {
        "counter": "get_apps_and_websites_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Rize — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON RIZE →

Instant setup, no code required.

FULL CATALOGUE

All 28 Rize tools

DESTRUCTIVE 3 tools

Destructive delete_client Delete a client Destructive delete_project Delete a project Destructive delete_task Delete a task

EXECUTE 2 tools

Execute start_session_timer Start a new focus session timer Execute stop_session_timer Stop the current session timer

WRITE 8 tools

Write create_client Create a new client Write create_project Create a new project Write create_session Create a new time session Write create_task Create a new task Write extend_current_session Extend the current session by specified minutes Write update_client Update an existing client Write update_project Update an existing project Write update_task Update an existing task

READ 15 tools

Read get_apps_and_websites Get apps and websites usage within a time range Read get_categories Get time spent by category within a time range Read get_client Get a specific client by ID Read get_client_time_entries Get time entries by client within a time range Read get_clients List all clients with optional filtering Read get_current_session Get the currently active session Read get_current_user Get the current authenticated user profile Read get_project Get a specific project by ID Read get_project_time_entries Get time entries by project within a time range Read get_projects List all projects with optional filtering Read get_sessions Get sessions within a time range Read get_summary Get productivity summary (total, focus, meeting, break time) within a time range Read get_task Get a specific task by ID Read get_task_time_entries Get time entries by task within a time range Read get_tasks List all tasks with optional filtering

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Rize

Can an AI agent delete data through the Rize MCP server? +

Yes. The Rize server exposes 3 destructive tools including delete_client, delete_project, delete_task. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Rize? +

The Rize server has 8 write tools including create_client, create_project, create_session. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Rize.

How many tools does the Rize MCP server expose? +

28 tools across 4 categories: Destructive, Execute, Read, Write. 15 are read-only. 13 can modify, create, or delete data.

How do I enforce a policy on Rize? +

Register the Rize MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Rize tool call.

Deterministic rules across all 28 Rize tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON RIZE →

Instant setup, no code required.

28 Rize tools catalogued and risk-classified — across an index of 43,000+ MCP servers.