AI agents call validate_json_2 to retrieve information from TinyFn without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
json_string | string | Yes | JSON string to validate |
Parameters from the server's own tool schema.
Validation tools that check data format and return pass/fail results are read-only operations. They retrieve information about the input (whether it is valid JSON) without creating, modifying, executing code, deleting data, or moving money. This tool has minimal blast radius if misused by an AI agent—it cannot harm systems or data.
From the tool's definition Tool description states 'Validate if a string is valid JSON' - this is a validation/checking operation with no side effects.
Attacks that exploit this kind of access
Validate if a string is valid JSON. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
validate_json_2 accepts 1 parameter: json_string. Required: json_string. The full parameter table on this page comes from the server's own tool schema.
Register the TinyFn MCP server in PolicyLayer and add a rule for validate_json_2: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches TinyFn. Nothing to install.
validate_json_2 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 validate_json_2 rule in your PolicyLayer 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 PolicyLayer policy for validate_json_2. 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.
validate_json_2 is provided by the TinyFn MCP server (https://api.tinyfn.io/mcp/all/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
validate_json_2 is one line of TinyFn's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →