connect_matrix_room_bus
Create a Matrix room scaffold with sanitized room events, reaction maps, approval policy, adapter source, and token/encryption safety notes.
This record as markdown: /tools/io-github-pantani-tdmcp/connect-matrix-room-bus.md
What connect_matrix_room_bus does on tdmcp — TouchDesigner MCP server
AI agents use connect_matrix_room_bus 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_matrix_room_bus is rated Medium
This tool creates a new resource (a Matrix room scaffold) with associated metadata and policies. It is reversible (the room can be deleted or modified later), and the blast radius is moderate — misconfiguration could create unintended rooms, expose tokens, or establish incorrect approval policies, but does not directly execute code, delete data irreversibly, or move money.
From the tool's definition Tool description states 'Create a Matrix room scaffold' — the verb 'Create' indicates data creation. The parameters mention 'sanitized room events, reaction maps, approval policy, adapter source, and token/encryption' which are configuration structures being…
Attacks that exploit this kind of access
The rule that runs connect_matrix_room_bus 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_matrix_room_bus, this is the rule to start with:
connect_matrix_room_bus 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_matrix_room_bus call is checked against it from then on.
Questions about connect_matrix_room_bus
Create a Matrix room scaffold with sanitized room events, reaction maps, approval policy, adapter source, and token/encryption safety notes. 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_matrix_room_bus: 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_matrix_room_bus 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_matrix_room_bus 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_matrix_room_bus. 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_matrix_room_bus 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