// SCAN REPORT

MCP Node Js TypeScript API

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

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

Last updated: 4 Jul 2026

6 can modify or destroy data

4 read-only

10 tools total

Community server · catalogue entry verified 04/07/2026

How to control MCP Node Js TypeScript API ↓

TOOL MAP

What MCP Node Js TypeScript API exposes to your agents

Read (4) Write / Execute (4) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous MCP Node Js TypeScript API tools

Destructive · High delete_product The tool performs an irreversible deletion operation on persistent data. Destructive · High delete_user This tool permanently removes user records from MongoDB without possibility of recovery (unless backups exist outside the tool's control). Write · Medium create_product This tool creates new records in the product database, which is a reversible write operation. Write · Medium create_user This tool creates new data (a user record) in the database.

6 of MCP Node Js TypeScript API's 10 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 Node Js TypeScript API

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

Deny destructive operations

{
  "delete_product": {
    "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_product": {
    "limits": [
      {
        "counter": "create_product_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_all_products": {
    "limits": [
      {
        "counter": "get_all_products_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 Node Js TypeScript API — 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 NODE JS TYPESCRIPT API →

Instant setup, no code required.

FULL CATALOGUE

All 10 MCP Node Js TypeScript API tools

DESTRUCTIVE 2 tools

Destructive delete_product Delete a product by its ID Destructive delete_user Delete a user by their ID

WRITE 4 tools

Write create_product Create a new product with name, description, price, quantity, measure type, and attributes Write create_user Create a new user with email, password, name, and optional picture URL Write update_product Update an existing product by ID Write update_user Update an existing user by ID

READ 4 tools

Read get_all_products Retrieve all products from the database Read get_all_users Retrieve all users from the database Read get_product_by_id Get a specific product by its ID Read get_user_by_id Get a specific user by their ID

EXPLORE

Related servers

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

FAQ

Questions about MCP Node Js TypeScript API

Can an AI agent delete data through the MCP Node Js TypeScript API MCP server? +

Yes. The MCP Node Js TypeScript API server exposes 2 destructive tools including delete_product, delete_user. 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 MCP Node Js TypeScript API? +

The MCP Node Js TypeScript API server has 4 write tools including create_product, create_user, update_product. 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 Node Js TypeScript API.

How many tools does the MCP Node Js TypeScript API MCP server expose? +

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

How do I enforce a policy on MCP Node Js TypeScript API? +

Register the MCP Node Js TypeScript API 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 Node Js TypeScript API tool call.

Deterministic rules across all 10 MCP Node Js TypeScript API tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MCP NODE JS TYPESCRIPT API →

Instant setup, no code required.

10 MCP Node Js TypeScript API tools catalogued and risk-classified — across an index of 43,000+ MCP servers.