AI agents call validate_base64 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 |
|---|---|---|---|
base64_str | string | Yes | Base64 string to validate |
Parameters from the server's own tool schema.
This is a deterministic validation utility that only checks whether input conforms to base64 format. It retrieves or queries the state of data (whether it is valid base64) without side effects, making it a Read operation. The severity is low because misuse would only return true/false validation results with no blast radius.
From the tool's definition Tool name 'validate_base64' and description 'Validate a base64 string' indicate a validation/checking operation with no data modification, creation, deletion, or execution capability.
Attacks that exploit this kind of access
Validate a base64 string. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
validate_base64 accepts 1 parameter: base64_str. Required: base64_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_base64: 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_base64 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_base64 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_base64. 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_base64 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_base64 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 →