append_replan_note
AI agents use append_replan_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.
The tool appears to modify planning notes/metadata within a project management system. This is a reversible write operation on structured data (plans, tasks, notes) rather than executing code, deleting data, or moving funds. The empty description limits confidence, but the naming pattern and context of sibling tools strongly suggest it appends data to a note field.
From the tool's definition Tool name 'append_replan_note' indicates appending/adding notes to a replanning context. Sibling tools like 'append_task_note', 'edit_task', 'add_task' are all Write operations that modify plan/task state.
Attacks that exploit this kind of access
append_replan_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_replan_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_replan_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_replan_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_replan_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_replan_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 →