Appends modified files information to a trellis issue in the task trellis system Use this tool to record files that have been modified during task execution, along with descriptions of the modifications made. This helps maintain a comprehensive record of changes associated with each work item for...
AI agents use append_modified_files to create or update resources in Task Trellis MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Task Trellis MCP environment.
This tool modifies metadata about an issue (appending file modification records) in a reversible manner. It does not delete data, execute arbitrary code, move funds, or trigger external operations.
From the tool's definition Tool description states it 'Appends modified files information to a trellis issue' and 'record files that have been modified' — these are create/append operations that add data to an existing issue record.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access append_modified_files gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Task Trellis MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for append_modified_files:
{
"version": "1",
"default": "deny",
"tools": {
"append_modified_files": {
"limits": [
{
"counter": "append_modified_files_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}append_modified_files 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.
Free to start. No card required.
Appends modified files information to a trellis issue in the task trellis system Use this tool to record files that have been modified during task execution, along with descriptions of the modifications made. This helps maintain a comprehensive record of changes associated with each work item for tracking and audit purposes. File modification tracking purposes: - Record which files were changed during task execution - Document the nature of changes made to each file - Maintain audit trail of file-level modifications - Support code review and change management processes - Enable impact analysis for future changes Input requirements: - Issue ID: The unique identifier of the trellis issue to update - Files Changed: A record mapping file paths to descriptions of modifications File path guidelines: - Use relative paths from project root (e.g.,. It is categorised as a Write tool in the Task Trellis MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Task Trellis MCP server in PolicyLayer and add a rule for append_modified_files: 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 Task Trellis MCP. Nothing to install.
append_modified_files 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 append_modified_files 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 append_modified_files. 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.
append_modified_files is provided by the Task Trellis MCP server (langadventurellc/task-trellis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Task Trellis MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 Task Trellis MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.