diff_text
Compare two texts line by line and show added/removed lines.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/diff-text.md
What diff_text does on UnClick
AI agents call diff_text to retrieve information from UnClick 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 (original). |
text_b | string | Yes | Second text (modified). |
Parameters from the server's own tool schema.
Why diff_text is rated Low
This is a text comparison/diff utility that analyzes two texts and outputs the differences. No side effects occur—neither input text is modified, no external state changes, and no code execution or deletion happens. The tool only retrieves and displays differential analysis, making it a straightforward Read category operation with minimal risk.
From the tool's definition Tool performs comparison and shows differences without modifying either input text. Keywords: 'Compare', 'show added/removed lines' indicate read-only analysis of data.
Attacks that exploit this kind of access
The rule that runs diff_text safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For diff_text, this is the rule to start with:
diff_text 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 UnClick, apply this rule, and every diff_text call is checked against it from then on.
Questions about diff_text
Compare two texts line by line and show added/removed lines. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
diff_text accepts 2 parameters: text_a, text_b. Required: text_a, text_b. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for diff_text: 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 UnClick. Nothing to install.
diff_text 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 diff_text 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 diff_text. 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.
diff_text is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue