Add a bookmark to a specific location in the file
AI agents use imhex_bookmark_add to create or update resources in ImHex MCP Integration — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ImHex MCP Integration environment.
Adding a bookmark is a reversible write operation that creates or modifies metadata within the ImHex application state. It does not read sensitive data, execute arbitrary code, delete anything, or move money. Bookmarks are user annotations and can be removed, making this a harmless Write action with minimal blast radius.
From the tool's definition Tool name 'imhex_bookmark_add' and description 'Add a bookmark to a specific location in the file' indicate creation of a new bookmark record/marker.
Documented attack patterns abuse exactly the kind of access imhex_bookmark_add gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ImHex MCP Integration, and nothing reaches the server without passing your rules. This is the rule we recommend for imhex_bookmark_add:
{
"version": "1",
"default": "deny",
"tools": {
"imhex_bookmark_add": {
"limits": [
{
"counter": "imhex_bookmark_add_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} imhex_bookmark_add 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.
Add a bookmark to a specific location in the file. It is categorised as a Write tool in the ImHex MCP Integration MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ImHex MCP Integration MCP server in PolicyLayer and add a rule for imhex_bookmark_add: 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 ImHex MCP Integration. Nothing to install.
imhex_bookmark_add 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 imhex_bookmark_add 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 imhex_bookmark_add. 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.
imhex_bookmark_add is provided by the ImHex MCP Integration MCP server (jmpnop/imhexmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ImHex MCP Integration, 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.
27 ImHex MCP Integration tools catalogued and risk-classified — across an index of 43,000+ MCP servers.