// SCAN REPORT

Ui

38 tools. 25 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 4 Apr 2026

25 can modify or destroy data

13 read-only

38 tools total

// TOOL MAP

Read (13) Write / Execute (24) Destructive / Financial (1)

// WHAT CAN GO WRONG

Financial operations (payments_refund) can move real money. An agent caught in a loop could drain accounts before anyone notices.

Write operations (assess_legacy_codebase, audit_accessibility, figma_push_variables) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

Execute tools (forge_assess, forge_gate) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.

One command. Full control.

Intercept sits between your agent and Ui. Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.

npx -y @policylayer/intercept scan -- npx -y @forgespace/ui-mcp

Scans every tool. Generates a policy. Starts enforcing.

Works with Claude Code · Cursor · Claude Desktop · Windsurf · any MCP client

// RECOMMENDED RULES

Block financial tools by default

payments_refund:
  rules:
    - action: deny

Financial tools should be explicitly enabled per use case, not open by default.

Rate limit write operations

assess_legacy_codebase:
  rules:
    - rate_limit: 30/hour

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

analyze_component_library:
  rules:
    - rate_limit: 60/minute

Controls API costs and prevents retry loops from exhausting upstream rate limits.

// ALL 38 UI TOOLS

FINANCIAL 1 tools

Financial payments_refund

EXECUTE 2 tools

Execute forge_assess Execute forge_gate

READ 13 tools

Read analyze_component_library Read analyze_design_image_for_training Read analyze_design_references Read fetch_design_inspiration Read figma_context_parser Read forge_diff Read forge_scan Read get_available_components Read get_available_libraries Read get_component_library_status Read get_project_context Read list_projects Read validate_component_library_setup

// FAQ

Can an AI agent move money through the Ui MCP server? +

Yes. The Ui server exposes 1 financial tools including payments_refund. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. Intercept lets you block financial tools by default or set per-tool rate limits.

How do I prevent bulk modifications through Ui? +

The Ui server has 22 write tools including assess_legacy_codebase, audit_accessibility, figma_push_variables. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.

How many tools does the Ui MCP server expose? +

38 tools across 4 categories: Execute, Financial, Read, Write. 13 are read-only. 25 can modify, create, or delete data.

How do I add Intercept to my Ui setup? +

One line change. Instead of running the Ui server directly, prefix it with Intercept: intercept -c io-github-forge-space-ui-mcp.yaml -- npx -y @@forgespace/ui-mcp. Download a pre-built policy from policylayer.com/policies/io-github-forge-space-ui-mcp and adjust the limits to match your use case.

// RELATED SERVERS

Other MCP servers with similar tools.

Starter policies available for each. Same risk classification, same one-command setup.

policylayer/intercept

Control every MCP tool call
your agent makes.

Set budgets, approvals, and hard limits across MCP servers.

npx -y @policylayer/intercept init

Protect your agent in 30 seconds. Scans your MCP config and generates enforcement policies for every server.

Ui

One command. Full control.

Other MCP servers with similar tools.

Control every MCP tool call your agent makes.

Control every MCP tool call
your agent makes.