Create a bookmark at an address with a category and comment.
AI agents use set_bookmark to create or update resources in Kawaiidra MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kawaiidra MCP environment.
This tool creates bookmarks—metadata artifacts that annotate binary analysis results. Bookmarks are non-destructive, reversible metadata (comments can be deleted or modified), and have no side effects on the actual binary or system. It is clearly a Write operation rather than Execute or Destructive.
From the tool's definition Tool name is 'set_bookmark' and description states 'Create a bookmark at an address with a category and comment.' The verb 'Create' combined with storing metadata (bookmark, category, comment) indicates a write operation that creates reversible annotations.
Documented attack patterns abuse exactly the kind of access set_bookmark gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kawaiidra MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for set_bookmark:
{
"version": "1",
"default": "deny",
"tools": {
"set_bookmark": {
"limits": [
{
"counter": "set_bookmark_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} set_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.
Create a bookmark at an address with a category and comment. It is categorised as a Write tool in the Kawaiidra MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kawaiidra MCP server in PolicyLayer and add a rule for set_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 Kawaiidra MCP. Nothing to install.
set_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 set_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 set_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.
set_bookmark is provided by the Kawaiidra MCP server (wagonbomb/kawaiidra-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kawaiidra 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.
94 Kawaiidra MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.