AI agents call base64_encode 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 |
|---|---|---|---|
text | string | Yes | Text to encode |
Parameters from the server's own tool schema.
Base64 encoding is a reversible text transformation that does not alter, delete, or execute anything. It is a utility function for data representation. While encoding could theoretically be misused in a supply chain attack (e.g., obfuscating malicious payloads), the tool itself performs no actions — it merely transforms data according to a well-defined algorithm.
From the tool's definition Tool description states 'Encode text to base64' — this is a deterministic encoding/transformation operation with no side effects. No data is deleted, modified, executed, or financially committed. It reads input and produces encoded output.
Attacks that exploit this kind of access
Encode text to base64. Properly handles Unicode. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
base64_encode accepts 1 parameter: text. Required: text. 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 base64_encode: 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.
base64_encode 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 base64_encode 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 base64_encode. 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.
base64_encode 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.
base64_encode 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 →