ui_diff

Compare the current UI state against a previous snapshot to detect changes.

SERVERIconnect SOURCEiconnect-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-heznpc-iconnect/ui-diff.md

WHAT IT DOES

What ui_diff does on Iconnect

AI agents call ui_diff to retrieve information from Iconnect without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why ui_diff is rated Low

This is fundamentally a data retrieval and analysis tool. It queries the current UI state and compares it against a stored snapshot to identify differences. There are no side effects, no data modification, no code execution, and no irreversible actions. The tool only reads and reports on UI state information, making it a Read category risk with low severity.

From the tool's definition Tool compares and detects changes between UI states; it 'Compare[s] the current UI state against a previous snapshot' with no mention of modification, deletion, or execution of external operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ui_diff safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ui_diff, this is the rule to start with:

ui_diff Allowed

ui_diff is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ui_diff": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every ui_diff call is checked against it from then on.

FAQ

Questions about ui_diff

What does the ui_diff tool do? +

Compare the current UI state against a previous snapshot to detect changes. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ui_diff? +

Register the Iconnect MCP server in PolicyLayer and add a rule for ui_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 Iconnect. Nothing to install.

What risk level is ui_diff? +

ui_diff is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ui_diff? +

Yes. Add a rate_limit block to the ui_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.

How do I block ui_diff completely? +

Set action: deny in the PolicyLayer policy for ui_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.

What MCP server provides ui_diff? +

ui_diff is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Iconnect, and thousands of servers like it.

This server

All 279 Iconnect tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →