encoding

Encoder / Decoder (base64 / url / hex) — Reversibly encode or decode text between base64, base64url, URL-percent and hex.

SERVERGateway SOURCEhttps://wingmanprotocol.com/mcp

Low RISK CLASS

Category Read

Parameters 31 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-wingmanprotocol-agent-gateway/encoding.md

WHAT IT DOES

What encoding does on Gateway

AI agents call encoding to retrieve information from Gateway 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
`op`	string	—	Direction
`text`	string	Yes	Text or encoded payload to convert
`scheme`	string	—	Wire format

Parameters from the server's own tool schema.

RISK

Why encoding is rated Low

Encoding and decoding are reversible transformations of text format (base64, URL-percent, hex). They do not create, modify, delete, or execute operations on any persistent state or external systems. The tool merely converts between representations of data.

From the tool's definition Tool description states 'Reversibly encode or decode text' — these are transformations with no persistence or side effects. Encoding/decoding is data retrieval and representation conversion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs encoding safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For encoding, this is the rule to start with:

encoding Allowed

encoding is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "encoding": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every encoding call is checked against it from then on.

FAQ

Questions about encoding

What does the encoding tool do? +

Encoder / Decoder (base64 / url / hex) — Reversibly encode or decode text between base64, base64url, URL-percent and hex. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.

What parameters does encoding accept? +

encoding accepts 3 parameters: op, text, scheme. Required: text. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on encoding? +

Register the Gateway MCP server in PolicyLayer and add a rule for encoding: 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 Gateway. Nothing to install.

What risk level is encoding? +

encoding is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit encoding? +

Yes. Add a rate_limit block to the encoding 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.

How do I block encoding completely? +

Set action: deny in the PolicyLayer policy for encoding. 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.

What MCP server provides encoding? +

encoding is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Gateway, and thousands of servers like it.

This server

All 271 Gateway tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →