line_ending_convert
Line Ending Converter — Detect and normalize line endings (LF/CRLF/CR) in text to a single target style.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/line-ending-convert.md
What line_ending_convert does on Gateway
AI agents use line_ending_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 |
|---|---|---|---|
text | string | Yes | Text to convert |
target | string | — | lf | crlf | cr (default lf) |
Parameters from the server's own tool schema.
Why line_ending_convert is rated Medium
This tool modifies text by converting line endings from one format to another. While the transformation is reversible (line endings can be converted back), it constitutes a Write operation because it alters data. The severity is low because line ending normalization is a safe, non-destructive text operation with minimal blast radius—it cannot delete data, execute arbitrary code, or cause financial harm.
From the tool's definition Tool description states it 'normalize[s] line endings... in text to a single target style', which indicates modification of data. The name 'line_ending_convert' and description confirm this is a transformation operation that rewrites content.
Attacks that exploit this kind of access
The rule that runs line_ending_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 line_ending_convert, this is the rule to start with:
line_ending_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 line_ending_convert call is checked against it from then on.
Questions about line_ending_convert
Line Ending Converter — Detect and normalize line endings (LF/CRLF/CR) in text to a single target style. 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.
line_ending_convert accepts 2 parameters: text, target. Required: text. 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 line_ending_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.
line_ending_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 line_ending_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 line_ending_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.
line_ending_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