// SCAN REPORT

MCP Authentication Demo

5 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 12 Jun 2026

2 can modify or destroy data

3 read-only

5 tools total

Community server · catalogue entry verified 12/06/2026

How to control MCP Authentication Demo ↓

TOOL MAP

What MCP Authentication Demo exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous MCP Authentication Demo tools

Write · Medium createExampleData This tool creates new data items, which is a reversible write operation. Write · Medium updateExampleData This tool modifies existing data owned by the authenticated user.

2 of MCP Authentication Demo's 5 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control MCP Authentication Demo

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

Rate limit write operations

{
  "createExampleData": {
    "limits": [
      {
        "counter": "createexampledata_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "getUserProfile": {
    "limits": [
      {
        "counter": "getuserprofile_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 MCP Authentication Demo — 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 MCP AUTHENTICATION DEMO →

Free to start. No card required.

FULL CATALOGUE

All 5 MCP Authentication Demo tools

WRITE 2 tools

Write createExampleData Creates a new example data item for the authenticated user. Demonstrates authenticated CRUD operations with in Write updateExampleData Updates an existing example data item owned by the authenticated user. Demonstrates ownership validation and p

READ 3 tools

Read getUserProfile Returns the authenticated user Read listExampleData Retrieves a list of the authenticated user Read ping Health check endpoint that works without authentication. Useful for testing MCP server connectivity.

FAQ

Questions about MCP Authentication Demo

How do I prevent bulk modifications through MCP Authentication Demo? +

The MCP Authentication Demo server has 2 write tools including createExampleData, updateExampleData. 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 MCP Authentication Demo.

How many tools does the MCP Authentication Demo MCP server expose? +

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

How do I enforce a policy on MCP Authentication Demo? +

Register the MCP Authentication Demo 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 MCP Authentication Demo tool call.

Deterministic rules across all 5 MCP Authentication Demo tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MCP AUTHENTICATION DEMO →

Free to start. No card required.

5 MCP Authentication Demo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.