append_task_note
AI agents use append_task_note to create or update resources in Keshro MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Keshro MCP environment.
Appending a note to a task creates or modifies data reversibly—a characteristic Write operation. The tool does not delete (Destructive), execute code (Execute), move money (Financial), or run arbitrary commands. Severity is medium because malicious note injection in a high-stakes engineering project context could mislead or disrupt task coordination, but notes are typically recoverable and non-destructive.
From the tool's definition Tool name 'append_task_note' indicates modification of task notes; the empty description limits certainty but the naming pattern matches sibling tools like 'add_task' and 'edit_task' that are Write operations.
Attacks that exploit this kind of access
append_task_note. It is categorised as a Write tool in the Keshro MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Keshro MCP server in PolicyLayer and add a rule for append_task_note: 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 Keshro MCP. Nothing to install.
append_task_note 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_task_note 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_task_note. 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_task_note is provided by the Keshro MCP server (jlewitt1/keshro-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →