This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/util-base64.md
What util_base64 does on Delx Mcp A2a
AI agents call util_base64 to retrieve information from Delx Mcp A2a without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
input | string | Yes | String to encode or Base64 string to decode |
action | string | Yes | Action to perform |
Parameters from the server's own tool schema.
Why util_base64 is rated Low
Base64 encoding and decoding are purely computational operations that read input data and return transformed output without creating, modifying, deleting, or executing anything. This is a utility function for data format conversion, analogous to a standard library function. The operation is reversible and has no impact on system state or external resources.
From the tool's definition Tool performs encoding/decoding of Base64 strings, which are data transformation operations with no side effects, no external state changes, and no code execution.
Attacks that exploit this kind of access
The rule that runs util_base64 safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Mcp A2a, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For util_base64, this is the rule to start with:
util_base64 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx Mcp A2a, apply this rule, and every util_base64 call is checked against it from then on.
Questions about util_base64
Encode or decode Base64 strings. It is categorised as a Read tool in the Delx Mcp A2a MCP Server, which means it retrieves data without modifying state.
util_base64 accepts 2 parameters: input, action. Required: input, action. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Mcp A2a MCP server in PolicyLayer and add a rule for util_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 Delx Mcp A2a. Nothing to install.
util_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 util_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 util_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.
util_base64 is provided by the Delx Mcp A2a MCP server (https://api.delx.ai/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Mcp A2a, and thousands of servers like it.
This server
Across the catalogue