get_editor_context
Read compact project and editor state for references such as
This record as markdown: /tools/io-github-pantani-tdmcp/get-editor-context.md
What get_editor_context does on tdmcp — TouchDesigner MCP server
AI agents call get_editor_context 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 get_editor_context is rated Low
This tool queries and retrieves project metadata and editor state without side effects. It is a classic Read operation similar to 'get' or 'fetch' patterns. The low severity reflects that reading project state poses minimal risk—the worst outcome is information disclosure, not data loss or code execution.
From the tool's definition get_editor_context reads 'compact project and editor state for references'—a pure retrieval operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
The rule that runs get_editor_context 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 get_editor_context, this is the rule to start with:
get_editor_context 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 get_editor_context call is checked against it from then on.
Questions about get_editor_context
Read compact project and editor state for references such as. 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 get_editor_context: 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.
get_editor_context 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 get_editor_context 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 get_editor_context. 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.
get_editor_context 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