inspect_component_manifest
Read and validate a tdmcp component/library manifest from a package folder or file. Read-only: use it to check a package
This record as markdown: /tools/io-github-pantani-tdmcp/inspect-component-manifest.md
What inspect_component_manifest does on tdmcp — TouchDesigner MCP server
AI agents call inspect_component_manifest 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 inspect_component_manifest is rated Low
This tool retrieves and validates manifest metadata from a component/library package without altering any data. It performs a query/inspection operation with no side effects, fitting the Read category. Low severity because it only accesses configuration data with minimal blast radius if misused.
From the tool's definition Tool description explicitly states 'Read and validate' and 'Read-only: use it to check a package'. The verb 'inspect' and qualification 'Read-only' confirm no modification occurs.
Attacks that exploit this kind of access
The rule that runs inspect_component_manifest 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 inspect_component_manifest, this is the rule to start with:
inspect_component_manifest 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 inspect_component_manifest call is checked against it from then on.
Questions about inspect_component_manifest
Read and validate a tdmcp component/library manifest from a package folder or file. Read-only: use it to check a package. 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 inspect_component_manifest: 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.
inspect_component_manifest 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 inspect_component_manifest 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 inspect_component_manifest. 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.
inspect_component_manifest 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