connect_webrtc_browser_input
Create a browser/WebRTC input scaffold for webcam, screen, pointer, and sensor data supplied by an external signaling app.
This record as markdown: /tools/io-github-pantani-tdmcp/connect-webrtc-browser-input.md
What connect_webrtc_browser_input does on tdmcp — TouchDesigner MCP server
AI agents use connect_webrtc_browser_input 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.
Why connect_webrtc_browser_input is rated Medium
This tool sets up a new data input pipeline by creating WebRTC connection scaffolding. It modifies the project state by adding a new input configuration, but does not execute arbitrary code, delete data, or move money. The action is reversible and creates/modifies project structure, placing it in the Write category.
From the tool's definition The tool 'connect_webrtc_browser_input' creates a scaffold to establish WebRTC connections for capturing external data (webcam, screen, pointer, sensor). The word 'create' and 'scaffold' indicate object/configuration creation rather than querying or deletion.
Attacks that exploit this kind of access
The rule that runs connect_webrtc_browser_input 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 connect_webrtc_browser_input, this is the rule to start with:
connect_webrtc_browser_input 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.
The button opens the PolicyLayer dashboard: create your workspace, connect tdmcp — TouchDesigner MCP server, apply this rule, and every connect_webrtc_browser_input call is checked against it from then on.
Questions about connect_webrtc_browser_input
Create a browser/WebRTC input scaffold for webcam, screen, pointer, and sensor data supplied by an external signaling app. 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.
Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for connect_webrtc_browser_input: 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.
connect_webrtc_browser_input is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the connect_webrtc_browser_input 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 connect_webrtc_browser_input. 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.
connect_webrtc_browser_input 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.
More on tdmcp — TouchDesigner MCP server, and thousands of servers like it.
This server
Across the catalogue