Get the current change buffer size and enabled status.
AI agents call sdk_change_buffer_size to retrieve information from UI Bridge MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries configuration state (buffer size and enabled status) without modifying, executing external code, or causing destructive effects. It is a read-only getter for status information, fitting the Read category. Severity is low because misuse poses minimal risk—an agent cannot harm the UI or external systems merely by retrieving buffer configuration.
From the tool's definition Tool description states 'Get the current change buffer size and enabled status' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get the current change buffer size and enabled status. It is categorised as a Read tool in the UI Bridge MCP MCP Server, which means it retrieves data without modifying state.
Register the UI Bridge MCP server in PolicyLayer and add a rule for sdk_change_buffer_size: 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.
sdk_change_buffer_size is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the sdk_change_buffer_size 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.
Set action: deny in the PolicyLayer policy for sdk_change_buffer_size. 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.
sdk_change_buffer_size 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →