// SCAN REPORT

MCP Pytest Server

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

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

Last updated: 12 Jun 2026

3 can modify or destroy data

0 read-only

3 tools total

Community server · catalogue entry verified 12/06/2026

How to control MCP Pytest Server ↓

TOOL MAP

What MCP Pytest Server 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 MCP Pytest Server tools

Write · Low record_session_finish This tool writes/records data about a test session finishing. Write · Low record_session_start This tool writes a new test session entry to track the start of a pytest run. Write · Low record_test_outcome This tool writes test outcome data to some store (likely a database or log).

3 of MCP Pytest Server'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 MCP Pytest Server

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

Rate limit write operations

{
  "record_session_finish": {
    "limits": [
      {
        "counter": "record_session_finish_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Create a free account and register MCP Pytest Server — 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 PYTEST →

Free to start. No card required.

FULL CATALOGUE

All 3 MCP Pytest Server tools

WRITE 3 tools

Write record_session_finish Record the completion of a test session. Write record_session_start Record the start of a test session. Write record_test_outcome Record the outcome of a test.

EXPLORE

Related servers

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

FAQ

Questions about MCP Pytest Server

How do I prevent bulk modifications through MCP Pytest Server? +

The MCP Pytest Server server has 3 write tools including record_session_finish, record_session_start, record_test_outcome. 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 Pytest Server.

How many tools does the MCP Pytest Server MCP server expose? +

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

How do I enforce a policy on MCP Pytest Server? +

Register the MCP Pytest Server 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 Pytest Server tool call.

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

ENFORCE POLICY ON MCP PYTEST →

Free to start. No card required.

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