toml_to_json
TOML to JSON Converter — Parse a TOML v1.0.0 document into JSON-compatible data (datetimes rendered as ISO 8601 strings).
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/toml-to-json.md
What toml_to_json does on Gateway
AI agents call toml_to_json 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 |
|---|---|---|---|
toml | string | Yes | TOML document text |
Parameters from the server's own tool schema.
Why toml_to_json is rated Low
This tool performs data transformation (TOML → JSON) on input provided by the caller. Parsing and formatting are read operations: the tool retrieves/transforms data without creating, modifying, deleting, or executing anything. The conversion is deterministic and reversible.
From the tool's definition Tool description states 'Parse a TOML v1.0.0 document into JSON-compatible data' — a parse/convert operation with no modification to source data, no code execution, and no side effects.
Attacks that exploit this kind of access
The rule that runs toml_to_json 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 toml_to_json, this is the rule to start with:
toml_to_json 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 Gateway, apply this rule, and every toml_to_json call is checked against it from then on.
Questions about toml_to_json
TOML to JSON Converter — Parse a TOML v1.0.0 document into JSON-compatible data (datetimes rendered as ISO 8601 strings). It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
toml_to_json accepts 1 parameter: toml. Required: toml. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for toml_to_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 Gateway. Nothing to install.
toml_to_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 toml_to_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 toml_to_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.
toml_to_json 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.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue