// SCAN REPORT

YST KPI Daily Report Collector

6 tools. 4 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 4 Jul 2026

4 can modify or destroy data

2 read-only

6 tools total

Community server · catalogue entry verified 04/07/2026

How to control YST KPI Daily Report Collector ↓

TOOL MAP

What YST KPI Daily Report Collector exposes to your agents

Read (2) Write / Execute (3) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous YST KPI Daily Report Collector tools

Destructive · Medium clear_saved_cookies This tool irreversibly deletes persisted session cookies. Execute · High browser_login The server description explicitly mentions browser automation and Google OAuth login. Execute · High collect_reports The server uses browser automation (Playwright) to log into external KPI systems via Google OAuth and collect data. Write · Medium save_cookies_from_browser This tool writes/persists authentication cookies to storage, enabling future session reuse without re-authentication.

4 of YST KPI Daily Report Collector's 6 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control YST KPI Daily Report Collector

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

Deny destructive operations

{
  "clear_saved_cookies": {
    "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

{
  "save_cookies_from_browser": {
    "limits": [
      {
        "counter": "save_cookies_from_browser_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "check_login_status": {
    "limits": [
      {
        "counter": "check_login_status_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 YST KPI Daily Report Collector — 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 YST KPI DAILY REPORT COLLECTOR →

Instant setup, no code required.

FULL CATALOGUE

All 6 YST KPI Daily Report Collector tools

DESTRUCTIVE 1 tools

Destructive clear_saved_cookies 清除已保存的 Cookie

EXECUTE 2 tools

Execute browser_login browser_login Execute collect_reports collect_reports

WRITE 1 tools

Write save_cookies_from_browser 保存浏览器 Cookie（用于首次登录）

READ 2 tools

Read check_login_status check_login_status Read check_playwright_installation 检查 Playwright 浏览器驱动安装状态

EXPLORE

Related servers

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

FAQ

Questions about YST KPI Daily Report Collector

Can an AI agent delete data through the YST KPI Daily Report Collector MCP server? +

Yes. The YST KPI Daily Report Collector server exposes 1 destructive tools including clear_saved_cookies. 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 YST KPI Daily Report Collector? +

The YST KPI Daily Report Collector server has 1 write tools including save_cookies_from_browser. 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 YST KPI Daily Report Collector.

How many tools does the YST KPI Daily Report Collector MCP server expose? +

6 tools across 3 categories: Destructive, Read, Write. 2 are read-only. 4 can modify, create, or delete data.

How do I enforce a policy on YST KPI Daily Report Collector? +

Register the YST KPI Daily Report Collector 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 YST KPI Daily Report Collector tool call.

Deterministic rules across all 6 YST KPI Daily Report Collector tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON YST KPI DAILY REPORT COLLECTOR →

Instant setup, no code required.

6 YST KPI Daily Report Collector tools catalogued and risk-classified — across an index of 43,000+ MCP servers.