Test

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

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

Last updated:

3 can modify or destroy data
0 read-only
3 tools total
Read (0) Write / Execute (3) Destructive / Financial (0)

Execute tools (coverage, playwright, run) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.

One command. Full control.

Intercept sits between your agent and Test. Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.

npx -y @policylayer/intercept scan -- npx -y @paretools/test
Scans every tool. Generates a policy. Starts enforcing.
Works with Claude Code · Cursor · Claude Desktop · Windsurf · any MCP client
How many tools does the Test MCP server expose? +

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

How do I add Intercept to my Test setup? +

One line change. Instead of running the Test server directly, prefix it with Intercept: intercept -c io-github-dave-london-pare-test.yaml -- npx -y @@paretools/test. Download a pre-built policy from policylayer.com/policies/io-github-dave-london-pare-test and adjust the limits to match your use case.

Other MCP servers with similar tools.

Starter policies available for each. Same risk classification, same one-command setup.

policylayer/intercept

Control every MCP tool call
your agent makes.

Set budgets, approvals, and hard limits across MCP servers.

npx -y @policylayer/intercept init
Protect your agent in 30 seconds. Scans your MCP config and generates enforcement policies for every server.
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.