ui_diff

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

SERVERAirMCP SOURCEairmcp

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/heznpc-airmcp/ui-diff.md

WHAT IT DOES

What ui_diff does on AirMCP

AI agents call ui_diff to retrieve information from AirMCP 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 tool performs a read-only comparison of UI states. It retrieves current UI information and compares it against a stored snapshot to identify changes. No data is created, modified, deleted, or executed. The operation is purely analytical with no side effects on the system.

From the tool's definition Tool name 'ui_diff' and description 'Compare the current UI state against a previous snapshot to detect changes' indicate a comparison/query operation that retrieves and analyzes UI state information without modifying, executing, or deleting anything.

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 AirMCP, 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 AirMCP, 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 AirMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ui_diff? +

Register the Air 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 AirMCP. 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 Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Air, and thousands of servers like it.

This server

All 279 Air tools →

Across the catalogue

The MCP Attack Database →

Guides

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