style_memory
READ or UPDATE the long-lived Memory/style.md note in the configured Obsidian vault — the artist
This record as markdown: /tools/io-github-pantani-tdmcp/style-memory.md
What style_memory does on tdmcp — TouchDesigner MCP server
AI agents use style_memory 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 style_memory is rated Medium
While the tool permits both read and write operations, the explicit mention of UPDATE capability places it in the Write category. It creates or modifies data (a markdown note) reversibly—the note can be edited or reverted.
From the tool's definition Tool description states 'READ or UPDATE the long-lived Memory/style.md note' — the UPDATE operation indicates the tool modifies data in an external system (Obsidian vault).
Attacks that exploit this kind of access
The rule that runs style_memory 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 style_memory, this is the rule to start with:
style_memory 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 style_memory call is checked against it from then on.
Questions about style_memory
READ or UPDATE the long-lived Memory/style.md note in the configured Obsidian vault — the artist. 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 style_memory: 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.
style_memory 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 style_memory 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 style_memory. 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.
style_memory 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