Attach a persistent note to a file or symbol that surfaces inline in future read_relevant results. Call this immediately when you encounter: a known bug or race condition, fragile code that shouldn
AI agents use annotate to create or update resources in Local Rag — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local Rag environment.
This tool writes/creates persistent annotations in a semantic code search system. While reversible (annotations can be deleted via the sibling `delete_annotation` tool), it modifies system state and could pollute the codebase with misleading or malicious annotations if misused by an uncontrolled agent.
From the tool's definition Tool description states 'Attach a persistent note to a file or symbol' — creates and stores annotations that 'surfaces inline in future read_relevant results', indicating persistent modification of metadata.
Documented attack patterns abuse exactly the kind of access annotate gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Local Rag, and nothing reaches the server without passing your rules. This is the rule we recommend for annotate:
{
"version": "1",
"default": "deny",
"tools": {
"annotate": {
"limits": [
{
"counter": "annotate_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}annotate 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.
Attach a persistent note to a file or symbol that surfaces inline in future read_relevant results. Call this immediately when you encounter: a known bug or race condition, fragile code that shouldn. It is categorised as a Write tool in the Local Rag MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Local Rag MCP server in PolicyLayer and add a rule for annotate: 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 Local Rag. Nothing to install.
annotate 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 annotate 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 annotate. 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.
annotate is provided by the Local Rag MCP server (thewinci/mimirs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Local Rag, 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.
29 Local Rag tools catalogued and risk-classified — across an index of 43,000+ MCP servers.