// SCAN REPORT

StressZero MCP - Burnout Risk Scoring

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

1 write tool that can modify data. Rate limits recommended.

Last updated: 1 Jul 2026

1 can modify or destroy data

3 read-only

4 tools total

Community server · catalogue entry verified 01/07/2026

How to control StressZero MCP - Burnout Risk Scoring ↓

TOOL MAP

What StressZero MCP - Burnout Risk Scoring exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous StressZero MCP - Burnout Risk Scoring tools

Write · Medium get_stresszero_api_key The tool creates a new API key, which is a Write operation (creating a credential resource).

1 of StressZero MCP - Burnout Risk Scoring's 4 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control StressZero MCP - Burnout Risk Scoring

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

Rate limit write operations

{
  "get_stresszero_api_key": {
    "limits": [
      {
        "counter": "get_stresszero_api_key_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "analyze_burnout": {
    "limits": [
      {
        "counter": "analyze_burnout_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 StressZero MCP - Burnout Risk Scoring — 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 STRESSZERO MCP - BURNOUT RISK SCORING →

Instant setup, no code required.

FULL CATALOGUE

All 4 StressZero MCP - Burnout Risk Scoring tools

WRITE 1 tools

Write get_stresszero_api_key Create a free StressZero API key (500 calls/month).

READ 3 tools

Read analyze_burnout Score burnout risk across 3 dimensions (physical, emotional, effectiveness). Read generate_burnout_report Generate a comprehensive burnout assessment report with dimension-by-dimension analysis, Read quick_burnout_check Simplified burnout screening with just 3 scores (one per dimension).

FAQ

Questions about StressZero MCP - Burnout Risk Scoring

How do I prevent bulk modifications through StressZero MCP - Burnout Risk Scoring? +

The StressZero MCP - Burnout Risk Scoring server has 1 write tools including get_stresszero_api_key. 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 StressZero MCP - Burnout Risk Scoring.

How many tools does the StressZero MCP - Burnout Risk Scoring MCP server expose? +

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

How do I enforce a policy on StressZero MCP - Burnout Risk Scoring? +

Register the StressZero MCP - Burnout Risk Scoring 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 StressZero MCP - Burnout Risk Scoring tool call.

Deterministic rules across all 4 StressZero MCP - Burnout Risk Scoring tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON STRESSZERO MCP - BURNOUT RISK SCORING →

Instant setup, no code required.

4 StressZero MCP - Burnout Risk Scoring tools catalogued and risk-classified — across an index of 43,000+ MCP servers.