indent_convert
Indentation Converter (tabs <-> spaces) — Convert each line's LEADING indentation only between tabs and spaces, leaving content elsewhere on the line untouched.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/indent-convert.md
What indent_convert does on Gateway
AI agents use indent_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 |
|---|---|---|---|
mode | string | Yes | tabs_to_spaces | spaces_to_tabs |
text | string | Yes | Text to convert |
width | integer | — | Spaces per tab stop, 1-16 (default 4) |
Parameters from the server's own tool schema.
Why indent_convert is rated Medium
This tool modifies document/code formatting by converting indentation styles. While the modifications are reversible (can convert back), it performs a data transformation operation that changes the state of content. This is characteristic of Write-category tools. Severity is low because the changes are cosmetic (whitespace-only), limited in scope (leading indentation only), and easily undone.
From the tool's definition Tool description states it 'Convert[s] each line's LEADING indentation' and modifies content (converting between tabs and spaces), which constitutes reversible modification of data.
Attacks that exploit this kind of access
The rule that runs indent_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 indent_convert, this is the rule to start with:
indent_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 indent_convert call is checked against it from then on.
Questions about indent_convert
Indentation Converter (tabs <-> spaces) — Convert each line's LEADING indentation only between tabs and spaces, leaving content elsewhere on the line untouched. 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.
indent_convert accepts 3 parameters: mode, text, width. Required: mode, 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 indent_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.
indent_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 indent_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 indent_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.
indent_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