create_pop_field

Build a GPU point field using TouchDesigner

Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about create_pop_field

What does the create_pop_field tool do? +

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.

How do I enforce a policy on create_pop_field? +

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.

What risk level is create_pop_field? +

create_pop_field is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_pop_field? +

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.

How do I block create_pop_field completely? +

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.

What MCP server provides create_pop_field? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of tdmcp — TouchDesigner MCP server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.