text_diff
Text Diff (unified) — Unified line diff between two texts, with a similarity ratio and added/removed line counts.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/text-diff.md
What text_diff does on Gateway
AI agents call text_diff 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_a | string | Yes | First text |
text_b | string | Yes | Second text |
context | integer | — | Context lines around each change (default 3) |
to_label | string | — | Label for text_b in the diff header (default 'b') |
from_label | string | — | Label for text_a in the diff header (default 'a') |
Parameters from the server's own tool schema.
Why text_diff is rated Low
This tool retrieves and compares data without side effects. It reads two text inputs and returns analytical output (diff, similarity metrics). It does not create, modify, delete, execute code, or trigger external operations. It is purely informational/analytical in nature.
From the tool's definition Tool performs 'unified line diff between two texts' with output of 'similarity ratio and added/removed line counts'. No modification, deletion, or execution of external operations occurs.
Attacks that exploit this kind of access
The rule that runs text_diff 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 text_diff, this is the rule to start with:
text_diff 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 text_diff call is checked against it from then on.
Questions about text_diff
Text Diff (unified) — Unified line diff between two texts, with a similarity ratio and added/removed line counts. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
text_diff accepts 5 parameters: text_a, text_b, context, to_label, from_label. Required: text_a, text_b. 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 text_diff: 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.
text_diff 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 text_diff 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 text_diff. 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.
text_diff 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