Extract and parse a JSON value embedded in messy LLM output. Strips ```json fences, leading/trailing prose, code comments, and tolerates other LLM-isms. Returns the first parseable value and where in the text it started.
Part of the Streamparse MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call extract_json_from_text to retrieve information from Streamparse without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though extract_json_from_text only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
extract_json_from_text:
rules:
- action: allowSee the full Streamparse policy for all 3 tools.
Agents calling read-class tools like extract_json_from_text have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Extract and parse a JSON value embedded in messy LLM output. Strips ```json fences, leading/trailing prose, code comments, and tolerates other LLM-isms. Returns the first parseable value and where in the text it started.. It is categorised as a Read tool in the Streamparse MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for extract_json_from_text. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Streamparse MCP server.
extract_json_from_text is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the extract_json_from_text rule in your Intercept policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the Intercept policy for extract_json_from_text. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
extract_json_from_text is provided by the Streamparse MCP server (@mukundakatta/streamparse-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.