// SCAN REPORT

Scouter

25 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 6 May 2026

1 can modify or destroy data

24 read-only

25 tools total

// TOOL MAP

Read (24) Write / Execute (1) Destructive / Financial (0)

// WHAT CAN GO WRONG

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

// RECOMMENDED RULES

Cap read operations

get_agent_info:
  rules:
    - rate_limit: 60/minute

Controls API costs and prevents retry loops from exhausting upstream rate limits.

// FAQ

Is the Scouter MCP server safe to use without restrictions? +

The Scouter server is primarily read-only with 24 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Scouter MCP server expose? +

25 tools across 2 categories: Execute, Read. 24 are read-only. 1 can modify, create, or delete data.

How do I add Intercept to my Scouter setup? +

One line change. Instead of running the Scouter server directly, prefix it with Intercept: intercept -c scouter.yaml -- npx -y @scouter-mcp-server. Download a pre-built policy from policylayer.com/policies/scouter and adjust the limits to match your use case.

// RELATED SERVERS

Other MCP servers with similar tools.

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

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

GET STARTED →