AI agents use append_issue_log 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.
The tool modifies existing issue data by appending content, making it a Write category action. Severity is medium because appending to logs could affect audit trails and issue tracking, but the operation is reversible (content can be removed or edited). The confidence is high given the clear description of the modification behavior.
From the tool's definition Tool description states it 'Appends content to an issue', which is a modification operation that creates or extends data reversibly.
Documented attack patterns abuse exactly the kind of access append_issue_log 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_issue_log:
{
"version": "1",
"default": "deny",
"tools": {
"append_issue_log": {
"limits": [
{
"counter": "append_issue_log_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}append_issue_log 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 content to an issue. 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_issue_log: 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_issue_log 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_issue_log 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_issue_log. 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_issue_log 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.