manage_project_brief
Reads or atomically replaces the versioned brief at <project_root>/.tdmcp/agent-brief.json.
This record as markdown: /tools/io-github-pantani-tdmcp/manage-project-brief.md
What manage_project_brief does on tdmcp — TouchDesigner MCP server
AI agents use manage_project_brief 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 manage_project_brief is rated Medium
The capability to "atomically replace" a versioned brief file is a write operation that alters project state. While not destructive (it maintains versions), it creates or overwrites configuration data that affects TouchDesigner project behavior. The atomic nature and versioning reduce but don't eliminate risk of misconfiguration.
From the tool's definition "atomically replaces" — indicates the tool modifies data. The description specifies it can both read and replace a versioned brief file, making modification/overwriting its primary risk.
Attacks that exploit this kind of access
The rule that runs manage_project_brief 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 manage_project_brief, this is the rule to start with:
manage_project_brief 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 manage_project_brief call is checked against it from then on.
Questions about manage_project_brief
Reads or atomically replaces the versioned brief at <project_root>/.tdmcp/agent-brief.json. 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 manage_project_brief: 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.
manage_project_brief 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 manage_project_brief 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 manage_project_brief. 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.
manage_project_brief 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