create_asemic_writing
Generate a page of procedural asemic writing — random-but-writing-like glyph strokes that flow left-to-right along stacked baselines but spell nothing. A Script SOP lays out
This record as markdown: /tools/io-github-pantani-tdmcp/create-asemic-writing.md
What create_asemic_writing does on tdmcp — TouchDesigner MCP server
AI agents use create_asemic_writing 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_asemic_writing is rated Medium
This tool creates new procedural visual content (asemic writing glyphs) within TouchDesigner's visual system. It is a Write operation because it generates/creates visual data structures reversibly—the output can be deleted or replaced without affecting external systems. It does not execute arbitrary code, delete data irreversibly, move money, or retrieve existing data.
From the tool's definition Tool name is 'create_asemic_writing' and description states 'Generate a page of procedural asemic writing'; the verb 'Generate' and context of creating visual elements in TouchDesigner indicates this creates new data (glyphs/graphics) rather than retrieving…
Attacks that exploit this kind of access
The rule that runs create_asemic_writing 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_asemic_writing, this is the rule to start with:
create_asemic_writing 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_asemic_writing call is checked against it from then on.
Questions about create_asemic_writing
Generate a page of procedural asemic writing — random-but-writing-like glyph strokes that flow left-to-right along stacked baselines but spell nothing. A Script SOP lays out. 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_asemic_writing: 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_asemic_writing 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_asemic_writing 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_asemic_writing. 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_asemic_writing 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