AI agents call validate_json 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_str | string | Yes | JSON string to validate |
Parameters from the server's own tool schema.
This is a read-only validation tool that checks JSON structure without creating, modifying, or deleting data. It has no capacity to execute code, make financial transactions, or cause destructive operations. Risk is minimal—worst case an agent receives incorrect validation feedback, which is low severity.
From the tool's definition Tool name 'validate_json' and description 'Validate JSON syntax' indicate a validation/parsing operation with no side effects. Returns boolean or validation result without modifying data.
Attacks that exploit this kind of access
Validate JSON syntax. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
validate_json accepts 1 parameter: json_str. Required: json_str. 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: 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 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 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. 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 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 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 →