collect_reports · YST KPI Daily Report Collector MCP

WHAT IT DOES

What collect_reports does on YST KPI Daily Report Collector

AI agents invoke collect_reports to trigger actions in YST KPI Daily Report Collector. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why collect_reports needs a policy

The server uses browser automation (Playwright) to log into external KPI systems via Google OAuth and collect data. 'collect_reports' most likely triggers this browser automation workflow — an external operation with side effects (authenticated sessions, external system interactions).

From the tool's definition Tool name 'collect_reports' on a server described as using 'browser automation' to 'automatically collect daily report data from KPI systems' with 'persistent session management'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

collect_reports Rate-limited

collect_reports stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "collect_reports": {
      "limits": [
        {
          "counter": "collect_reports_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches YST KPI Daily Report Collector, so you can run agents against it safely.

FAQ

Questions about collect_reports

What does the collect_reports tool do? +

collect_reports. It is categorised as a Execute tool in the YST KPI Daily Report Collector MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on collect_reports? +

Register the YST KPI Daily Report Collector MCP server in PolicyLayer and add a rule for collect_reports: 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 YST KPI Daily Report Collector. Nothing to install.

What risk level is collect_reports? +

collect_reports is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit collect_reports? +

Yes. Add a rate_limit block to the collect_reports 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.

How do I block collect_reports completely? +

Set action: deny in the PolicyLayer policy for collect_reports. 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.

What MCP server provides collect_reports? +

collect_reports is provided by the YST KPI Daily Report Collector MCP server (xuzan9396/yst_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.