// SCAN REPORT

MCP Server & Client Test Environment

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

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

Last updated: 4 Jul 2026

6 can modify or destroy data

8 read-only

14 tools total

Community server · catalogue entry verified 04/07/2026

How to control MCP Server & Client Test Environment ↓

TOOL MAP

What MCP Server & Client Test Environment exposes to your agents

Read (8) Write / Execute (6) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous MCP Server & Client Test Environment tools

Execute · High run_server_command This tool executes arbitrary terminal commands in the workspace, which has broad potential for side effects depending on what commands an AI agent chooses to run. Execute · Low cos The tool itself appears to be a simple mathematical cosine function (Read/Other), but it exists in a testing environment that includes shell command execution capabilities. Execute · Low factorial The tool description is nearly uninformative — it only says 'factorial of a number', which suggests a simple mathematical computation (Read/Other). Execute · Low power The tool name and description suggest a simple mathematical exponentiation operation (Read/Other level), but the server context explicitly mentions shell command execution capabilities.

6 of MCP Server & Client Test Environment's 14 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 Server & Client Test Environment

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Server & Client Test Environment, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "divide": {
    "limits": [
      {
        "counter": "divide_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "add": {
    "limits": [
      {
        "counter": "add_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 Server & Client Test Environment — 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 SERVER & CLIENT TEST ENVIRONMENT →

Instant setup, no code required.

FULL CATALOGUE

All 14 MCP Server & Client Test Environment tools

EXECUTE 4 tools

Execute cos cos of a number Execute factorial factorial of a number Execute power Power of two numbers Execute run_server_command Run a terminal command in workspace.

WRITE 2 tools

Write divide Divide two numbers Write sqrt Square root of a number

READ 8 tools

Read add Add two numbers Read cbrt Cube root of a number Read log log of a number Read multiply Multiply two numbers Read remainder remainder of two numbers divison Read sin sin of a number Read subtract Subtract two numbers Read tan tan of a number

EXPLORE

Related servers

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

FAQ

Questions about MCP Server & Client Test Environment

How do I prevent bulk modifications through MCP Server & Client Test Environment? +

The MCP Server & Client Test Environment server has 2 write tools including divide, sqrt. 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 Server & Client Test Environment.

How many tools does the MCP Server & Client Test Environment MCP server expose? +

14 tools across 2 categories: Execute, Write. 8 are read-only. 6 can modify, create, or delete data.

How do I enforce a policy on MCP Server & Client Test Environment? +

Register the MCP Server & Client Test Environment 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 Server & Client Test Environment tool call.

Deterministic rules across all 14 MCP Server & Client Test Environment tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MCP SERVER & CLIENT TEST ENVIRONMENT →

Instant setup, no code required.

14 MCP Server & Client Test Environment tools catalogued and risk-classified — across an index of 43,000+ MCP servers.