This record as markdown: /tools/io-github-pantani-tdmcp/provenance-stamp.md
What provenance_stamp does on tdmcp — TouchDesigner MCP server
AI agents use provenance_stamp 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 provenance_stamp is rated Medium
The tool 'Writes a' suggests it creates or modifies data (write operation). Given the incomplete description, confidence is reduced. The severity is medium because writing provenance metadata in a TouchDesigner project has limited blast radius—it modifies project annotations but not critical visual or financial systems. This is reversible and typically low-risk compared to destructive or execute operations.
From the tool's definition Tool name 'provenance_stamp' and description 'Writes a' (incomplete) indicate a write operation that modifies data.
Attacks that exploit this kind of access
The rule that runs provenance_stamp 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 provenance_stamp, this is the rule to start with:
provenance_stamp 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 provenance_stamp call is checked against it from then on.
Questions about provenance_stamp
Writes a. 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 provenance_stamp: 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.
provenance_stamp 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 provenance_stamp 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 provenance_stamp. 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.
provenance_stamp 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