connect_wifi_presence_bus
Create a Wi-Fi presence scaffold with aggregate occupancy rows, dwell buckets, privacy policy, adapter source, and device-privacy notes.
This record as markdown: /tools/io-github-pantani-tdmcp/connect-wifi-presence-bus.md
What connect_wifi_presence_bus does on tdmcp — TouchDesigner MCP server
AI agents use connect_wifi_presence_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_wifi_presence_bus is rated Medium
This tool creates new data structures and configurations within TouchDesigner related to Wi-Fi presence detection. While it constructs a scaffold (reversible, not destructive), it does modify the project state by adding new elements. The 'medium' severity reflects that misuse could create unwanted presence detection infrastructure or privacy-invasive configurations, but the effects are reversible.
From the tool's definition The tool description indicates it 'Create[s] a Wi-Fi presence scaffold' with various configuration elements (occupancy rows, dwell buckets, privacy policy, adapter source, device-privacy notes).
Attacks that exploit this kind of access
The rule that runs connect_wifi_presence_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_wifi_presence_bus, this is the rule to start with:
connect_wifi_presence_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_wifi_presence_bus call is checked against it from then on.
Questions about connect_wifi_presence_bus
Create a Wi-Fi presence scaffold with aggregate occupancy rows, dwell buckets, privacy policy, adapter source, and device-privacy 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_wifi_presence_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_wifi_presence_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_wifi_presence_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_wifi_presence_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_wifi_presence_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