checksum_and_verify_pack
Compute or verify SHA-256 checksums for tdmcp artifacts (.tox, .recipe.json, bundles).
This record as markdown: /tools/io-github-pantani-tdmcp/checksum-and-verify-pack.md
What checksum_and_verify_pack does on tdmcp — TouchDesigner MCP server
AI agents call checksum_and_verify_pack to retrieve information from tdmcp — TouchDesigner MCP server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why checksum_and_verify_pack is rated Low
This tool retrieves and compares cryptographic hash values to validate artifact integrity. It has no side effects, does not modify data, does not execute arbitrary code, and does not delete or move resources. It falls squarely into the Read category as a data integrity checking operation.
From the tool's definition The tool description states it 'Compute[s] or verify[ies] SHA-256 checksums' for TouchDesigner artifacts. Computing and verifying checksums are read-only operations that inspect data integrity without modifying, deleting, or executing code.
Attacks that exploit this kind of access
The rule that runs checksum_and_verify_pack 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 checksum_and_verify_pack, this is the rule to start with:
checksum_and_verify_pack is read-only, so it stays allowed. 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 checksum_and_verify_pack call is checked against it from then on.
Questions about checksum_and_verify_pack
Compute or verify SHA-256 checksums for tdmcp artifacts (.tox, .recipe.json, bundles). It is categorised as a Read tool in the tdmcp — TouchDesigner MCP server MCP Server, which means it retrieves data without modifying state.
Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for checksum_and_verify_pack: 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.
checksum_and_verify_pack is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the checksum_and_verify_pack 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 checksum_and_verify_pack. 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.
checksum_and_verify_pack 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