Update fields on an existing bookmark. Only the fields you pass are modified; omitted fields stay unchanged. Returns the updated bookmark.
AI agents use update-bookmark to create or update resources in Karakeep MCP server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Karakeep MCP server environment.
The tool modifies existing bookmark records by updating specified fields. This is a reversible write operation—the changes can be undone by subsequent updates. It does not delete data (which would be Destructive), execute arbitrary code (Execute), or involve financial transactions (Financial).
From the tool's definition Tool description: 'Update fields on an existing bookmark. Only the fields you pass are modified; omitted fields stay unchanged. Returns the updated bookmark.' This is a modification operation that changes existing data.
Documented attack patterns abuse exactly the kind of access update-bookmark gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Karakeep MCP server, and nothing reaches the server without passing your rules. This is the rule we recommend for update-bookmark:
{
"version": "1",
"default": "deny",
"tools": {
"update-bookmark": {
"limits": [
{
"counter": "update-bookmark_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update-bookmark 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.
Update fields on an existing bookmark. Only the fields you pass are modified; omitted fields stay unchanged. Returns the updated bookmark. It is categorised as a Write tool in the Karakeep MCP server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Karakeep MCP server MCP server in PolicyLayer and add a rule for update-bookmark: 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 Karakeep MCP server. Nothing to install.
update-bookmark 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 update-bookmark 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 update-bookmark. 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.
update-bookmark is provided by the Karakeep MCP server MCP server (karakeep-app/karakeep). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Karakeep MCP server, 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.
11 Karakeep MCP server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.