yaml_json_convert
YAML <-> JSON Converter — Convert a YAML document to JSON, or a JSON object to YAML, using a safe (non-code-executing) parser.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/yaml-json-convert.md
What yaml_json_convert does on Gateway
AI agents use yaml_json_convert to create or update resources in Gateway, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gateway environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
data | object | — | JSON object to serialize (direction=json_to_yaml) |
yaml | string | — | YAML text (direction=yaml_to_json) |
direction | string | Yes | yaml_to_json | json_to_yaml |
Parameters from the server's own tool schema.
Why yaml_json_convert is rated Medium
An AI agent can call yaml_json_convert faster than any human can review: one bad instruction and it creates or modifies resources in Gateway by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs yaml_json_convert 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 yaml_json_convert, this is the rule to start with:
yaml_json_convert stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 yaml_json_convert call is checked against it from then on.
Questions about yaml_json_convert
YAML <-> JSON Converter — Convert a YAML document to JSON, or a JSON object to YAML, using a safe (non-code-executing) parser. It is categorised as a Write tool in the Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
yaml_json_convert accepts 3 parameters: data, yaml, direction. Required: direction. 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 yaml_json_convert: 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.
yaml_json_convert is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the yaml_json_convert 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 yaml_json_convert. 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.
yaml_json_convert 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