whitespace_normalize
Whitespace Normalizer — Collapse runs of spaces/tabs, trim line edges, and cap consecutive blank lines in plain text.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/whitespace-normalize.md
What whitespace_normalize does on Gateway
AI agents call whitespace_normalize 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 |
|---|---|---|---|
text | string | Yes | Text to normalize |
trim_lines | boolean | — | Strip leading/trailing whitespace from each line (default true) |
collapse_spaces | boolean | — | Collapse space/tab runs within a line to one space (default true) |
max_blank_lines | integer | — | Max consecutive blank lines to keep, 0-10 (default 1) |
Parameters from the server's own tool schema.
Why whitespace_normalize is rated Low
This tool purely transforms text by normalizing whitespace — collapsing spaces/tabs, trimming edges, and capping blank lines. It has no side effects, does not write or store data, and operates only on the input text passed to it. It is a pure text-processing utility analogous to a read/transform operation.
From the tool's definition Collapse runs of spaces/tabs, trim line edges, and cap consecutive blank lines in plain text
Attacks that exploit this kind of access
The rule that runs whitespace_normalize 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 whitespace_normalize, this is the rule to start with:
whitespace_normalize 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 whitespace_normalize call is checked against it from then on.
Questions about whitespace_normalize
Whitespace Normalizer — Collapse runs of spaces/tabs, trim line edges, and cap consecutive blank lines in plain text. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
whitespace_normalize accepts 4 parameters: text, trim_lines, collapse_spaces, max_blank_lines. 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 whitespace_normalize: 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.
whitespace_normalize 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 whitespace_normalize 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 whitespace_normalize. 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.
whitespace_normalize 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