watch_parameter_changes

Opt-in: subscribe to

SERVERtdmcp — TouchDesigner MCP server SOURCE@dpantani/tdmcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-pantani-tdmcp/watch-parameter-changes.md

WHAT IT DOES

What watch_parameter_changes does on tdmcp — TouchDesigner MCP server

AI agents call watch_parameter_changes to retrieve information from tdmcp — TouchDesigner MCP server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why watch_parameter_changes is rated Low

This tool retrieves or monitors data (parameter change events) without creating, modifying, deleting, or executing operations. It is a read-only subscription/listener that observes state changes in TouchDesigner parameters. The low severity reflects minimal blast radius—an AI agent using this tool can only observe, not alter, the system.

From the tool's definition Tool name 'watch_parameter_changes' and description phrase 'subscribe to' indicates monitoring/observing parameter state changes without modifying them. The 'Opt-in' qualifier reinforces that this is a passive subscription mechanism.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs watch_parameter_changes 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 watch_parameter_changes, this is the rule to start with:

watch_parameter_changes Allowed

watch_parameter_changes is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "watch_parameter_changes": {}
  }
}

ALLOW ONLY 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 watch_parameter_changes call is checked against it from then on.

FAQ

Questions about watch_parameter_changes

What does the watch_parameter_changes tool do? +

Opt-in: subscribe to. It is categorised as a Read tool in the tdmcp — TouchDesigner MCP server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on watch_parameter_changes? +

Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for watch_parameter_changes: 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 watch_parameter_changes? +

watch_parameter_changes is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit watch_parameter_changes? +

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

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

watch_parameter_changes 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

review_changes on MCP Server PR Pilot → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →