create_pop_field
Build a GPU point field using TouchDesigner
This record as markdown: /tools/io-github-pantani-tdmcp/create-pop-field.md
What create_pop_field does on tdmcp — TouchDesigner MCP server
AI agents use create_pop_field 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 create_pop_field is rated Medium
The tool creates a new GPU point field node/component in the TouchDesigner environment. This is a Write operation — it adds/creates data (a visual node) in the project. It is reversible (nodes can be deleted), so it does not qualify as Destructive. No code execution, financial transaction, or shell command is implied. Severity is medium because misuse could clutter or alter a live visual system.
From the tool's definition 'Build a GPU point field using TouchDesigner' — creates a new visual element (point field) within the TouchDesigner project
Attacks that exploit this kind of access
The rule that runs create_pop_field 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_pop_field, this is the rule to start with:
create_pop_field 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 create_pop_field call is checked against it from then on.
Questions about create_pop_field
Build a GPU point field using TouchDesigner. 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 create_pop_field: 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.
create_pop_field 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 create_pop_field 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 create_pop_field. 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.
create_pop_field 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