sdk_click · UI Bridge MCP: Risk & Policy

WHAT IT DOES

What sdk_click does on UI Bridge MCP

AI agents invoke sdk_click to trigger actions in UI Bridge MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why sdk_click needs a policy

Clicking UI elements triggers external operations whose effects depend on arguments — buttons clicked could submit forms, delete data, initiate transactions, etc. The blast radius is high because an AI agent could click arbitrary UI controls in external applications. Confidence is moderate because the description is empty and we're inferring from the name and server context alone.

From the tool's definition Tool name 'sdk_click' implies a UI click action; server description states it 'interact[s] with UI elements' and supports 'SDK mode for external applications'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sdk_click Rate-limited

sdk_click stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sdk_click": {
      "limits": [
        {
          "counter": "sdk_click_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches UI Bridge MCP, so you can run agents against it safely.

FAQ

Questions about sdk_click

What does the sdk_click tool do? +

sdk_click. It is categorised as a Execute tool in the UI Bridge MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on sdk_click? +

Register the UI Bridge MCP server in PolicyLayer and add a rule for sdk_click: 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 UI Bridge MCP. Nothing to install.

What risk level is sdk_click? +

sdk_click is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit sdk_click? +

Yes. Add a rate_limit block to the sdk_click 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 sdk_click completely? +

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

sdk_click is provided by the UI Bridge MCP server (qontinui/ui-bridge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.