3 tools. 1 can modify or destroy data without limits.
1 write tool that can modify data. Rate limits recommended.
Last updated:
Execute tools (parse_partial_json) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
extract_json_from_text:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
The Streamparse server is primarily read-only with 2 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.
3 tools across 2 categories: Execute, Read. 2 are read-only. 1 can modify, create, or delete data.
One line change. Instead of running the Streamparse server directly, prefix it with Intercept: intercept -c io-github-mukundakatta-streamparse.yaml -- npx -y @@mukundakatta/streamparse-mcp. Download a pre-built policy from policylayer.com/policies/io-github-mukundakatta-streamparse and adjust the limits to match your use case.
Starter policies available for each. Same risk classification, same one-command setup.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.