send_osc_bundle · MCP2OSC MCP: Risk & Policy

WHAT IT DOES

What send_osc_bundle does on MCP2OSC

AI agents use send_osc_bundle to create or update resources in MCP2OSC — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP2OSC environment.

WHY IT NEEDS A POLICY

Why send_osc_bundle needs a policy

An AI agent can call send_osc_bundle faster than any human can review — one bad instruction and it creates or modifies resources in MCP2OSC by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_osc_bundle Rate-limited

send_osc_bundle stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "send_osc_bundle": {
      "limits": [
        {
          "counter": "send_osc_bundle_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about send_osc_bundle

What does the send_osc_bundle tool do? +

Send multiple OSC messages as a single OSC bundle with precise timing. It is categorised as a Write tool in the MCP2OSC MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on send_osc_bundle? +

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

What risk level is send_osc_bundle? +

send_osc_bundle is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit send_osc_bundle? +

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

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

send_osc_bundle is provided by the MCP2OSC MCP server (yyf/mcp2osc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.