// SCAN REPORT

Test 1

3 tools. 3 can modify or destroy data without limits.

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

Last updated: 5 Jul 2026

3 can modify or destroy data

0 read-only

3 tools total

Community server · catalogue entry verified 05/07/2026

How to control Test 1 ↓

TOOL MAP

What Test 1 exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Test 1 tools

Write · Low compress_local_image Compression modifies a file in place or creates a compressed version, which is a reversible write operation. Write · Medium compress_remote_image Compressing a remote image modifies the image data (lossy or lossless compression), which is a Write operation. Write · Medium resize_image This tool modifies image data reversibly.

3 of Test 1's 3 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Test 1

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

Rate limit write operations

{
  "compress_local_image": {
    "limits": [
      {
        "counter": "compress_local_image_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Create a free account and register Test 1 — 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 TEST 1 →

Instant setup, no code required.

FULL CATALOGUE

All 3 Test 1 tools

WRITE 3 tools

Write compress_local_image Compress a local image file Write compress_remote_image Compress a remote image file by giving the URL of the image Write resize_image Resize an image file

FAQ

Questions about Test 1

How do I prevent bulk modifications through Test 1? +

The Test 1 server has 3 write tools including compress_local_image, compress_remote_image, resize_image. 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 Test 1.

How many tools does the Test 1 MCP server expose? +

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

How do I enforce a policy on Test 1? +

Register the Test 1 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 Test 1 tool call.

Deterministic rules across all 3 Test 1 tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON TEST 1 →

Instant setup, no code required.

3 Test 1 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.