sdk_change_buffer_disable · UI Bridge MCP: Risk & Policy

WHAT IT DOES

What sdk_change_buffer_disable does on UI Bridge MCP

AI agents invoke sdk_change_buffer_disable 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_change_buffer_disable needs a policy

Disabling change buffering alters the operational behavior of the UI bridge/SDK system. This is an execution-level configuration change that affects how UI changes are tracked or batched. It is not a simple data read or write, but a control operation that triggers a change in system behavior.

From the tool's definition 'Disable change buffering' — modifies a system-level buffering configuration for UI interaction

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sdk_change_buffer_disable Rate-limited

sdk_change_buffer_disable 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_change_buffer_disable": {
      "limits": [
        {
          "counter": "sdk_change_buffer_disable_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_change_buffer_disable

What does the sdk_change_buffer_disable tool do? +

Disable change buffering. 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_change_buffer_disable? +

Register the UI Bridge MCP server in PolicyLayer and add a rule for sdk_change_buffer_disable: 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_change_buffer_disable? +

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

Can I rate-limit sdk_change_buffer_disable? +

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

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

sdk_change_buffer_disable 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.