xml_json_convert
XML <-> JSON Converter — Convert XML to a canonical JSON tag/attrib/text/children object, or that shape back to XML. Rejects DOCTYPE/ENTITY declarations (XXE guard).
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/xml-json-convert.md
What xml_json_convert does on Gateway
AI agents use xml_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 |
|---|---|---|---|
xml | string | — | XML text (direction=xml_to_json) |
data | object | — | {tag, attrib, text, children} object (direction=json_to_xml) |
direction | string | Yes | xml_to_json | json_to_xml |
Parameters from the server's own tool schema.
Why xml_json_convert is rated Medium
This tool creates or modifies data through format conversion. While it includes XXE protections (mitigating injection risks), the ability to convert user-supplied JSON into XML and presumably write or return that output qualifies as Write.
From the tool's definition Tool description states it converts XML to JSON and back: 'Convert XML to a canonical JSON tag/attrib/text/children object, or that shape back to XML.' The reverse conversion (JSON → XML) creates new XML output, which constitutes data creation/modification.
Attacks that exploit this kind of access
The rule that runs xml_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 xml_json_convert, this is the rule to start with:
xml_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 xml_json_convert call is checked against it from then on.
Questions about xml_json_convert
XML <-> JSON Converter — Convert XML to a canonical JSON tag/attrib/text/children object, or that shape back to XML. Rejects DOCTYPE/ENTITY declarations (XXE guard). 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.
xml_json_convert accepts 3 parameters: xml, data, 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 xml_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.
xml_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 xml_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 xml_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.
xml_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