sdk_submit · UI Bridge MCP: Risk & Policy

WHAT IT DOES

What sdk_submit does on UI Bridge MCP

AI agents invoke sdk_submit 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_submit needs a policy

Submitting a form is an external operation that sends data and triggers server-side processing. The effects depend on the form's content and could be irreversible (e.g., placing an order, sending a message, registering a user). This goes beyond a simple write as it executes an action in an external SDK application with potentially wide-ranging side effects.

From the tool's definition 'Submit the form containing the element in the SDK app' — triggers a form submission action in an external application

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sdk_submit Rate-limited

sdk_submit 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_submit": {
      "limits": [
        {
          "counter": "sdk_submit_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_submit

What does the sdk_submit tool do? +

Submit the form containing the element in the SDK app. 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_submit? +

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

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

Can I rate-limit sdk_submit? +

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

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

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