create_openxr_controller_bridge

Create an OpenXR/SteamVR controller input scaffold for pose, trigger, grip, thumbstick, and button streams supplied by an external adapter.

SERVERtdmcp — TouchDesigner MCP server SOURCE@dpantani/tdmcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-pantani-tdmcp/create-openxr-controller-bridge.md

WHAT IT DOES

What create_openxr_controller_bridge does on tdmcp — TouchDesigner MCP server

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

RISK

Why create_openxr_controller_bridge is rated Medium

This tool creates a new component or node scaffold within TouchDesigner to bridge OpenXR/SteamVR controller inputs. It is a creative/constructive action that adds new data to the project, making it a Write operation. No code execution, deletion, or financial transaction is implied. Misuse could clutter or disrupt a project but effects are reversible by removing the created nodes.

From the tool's definition "Create an OpenXR/SteamVR controller input scaffold" — creates a new scaffold/bridge structure in the TouchDesigner project

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_openxr_controller_bridge safely

PolicyLayer is an MCP gateway: it sits between your AI agents and tdmcp — TouchDesigner MCP server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_openxr_controller_bridge, this is the rule to start with:

create_openxr_controller_bridge Rate-limited

create_openxr_controller_bridge 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": {
    "create_openxr_controller_bridge": {
      "limits": [
        {
          "counter": "create_openxr_controller_bridge_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect tdmcp — TouchDesigner MCP server, apply this rule, and every create_openxr_controller_bridge call is checked against it from then on.

FAQ

Questions about create_openxr_controller_bridge

What does the create_openxr_controller_bridge tool do? +

Create an OpenXR/SteamVR controller input scaffold for pose, trigger, grip, thumbstick, and button streams supplied by an external adapter. It is categorised as a Write tool in the tdmcp — TouchDesigner MCP server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_openxr_controller_bridge? +

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

What risk level is create_openxr_controller_bridge? +

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

Can I rate-limit create_openxr_controller_bridge? +

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

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

create_openxr_controller_bridge is provided by the tdmcp — TouchDesigner MCP server MCP server (@dpantani/tdmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on tdmcp — TouchDesigner MCP server, and thousands of servers like it.

This server

All 507 tdmcp — TouchDesigner MCP server tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →