text_diff
Line-level diff of two texts (LCS): counts of added/removed lines plus a marked-up line list. Runs on smart-tools.xyz.
This record as markdown: /tools/io-github-9thshini-smart-tools/text-diff.md
What text_diff does on SmartTools
AI agents call text_diff to retrieve information from SmartTools 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 |
|---|---|---|---|
a | string | Yes | First (original) text |
b | string | Yes | Second (changed) text |
trim | boolean | — | Trim each line before comparing (default true) |
locale | string | — | Language for the source_url link (default en) |
ignore_case | boolean | — | Compare case-insensitively (default false) |
Parameters from the server's own tool schema.
Why text_diff is rated Low
Even though text_diff only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
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 SmartTools, 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 SmartTools, apply this rule, and every text_diff call is checked against it from then on.
Questions about text_diff
Line-level diff of two texts (LCS): counts of added/removed lines plus a marked-up line list. Runs on smart-tools.xyz. It is categorised as a Read tool in the SmartTools MCP Server, which means it retrieves data without modifying state.
text_diff accepts 5 parameters: a, b, trim, locale, ignore_case. Required: a, b. The full parameter table on this page comes from the server's own tool schema.
Register the SmartTools 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 SmartTools. 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 SmartTools MCP server (https://smart-tools.xyz/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SmartTools, and thousands of servers like it.
This server
Across the catalogue