New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_editor_context

Read compact project and editor state for references such as

Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about get_editor_context

What does the get_editor_context tool do? +

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.

How do I enforce a policy on get_editor_context? +

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.

What risk level is get_editor_context? +

get_editor_context is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_editor_context? +

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.

How do I block get_editor_context completely? +

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.

What MCP server provides get_editor_context? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of tdmcp — TouchDesigner MCP server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.