AI agents use add_clawmark to create or update resources in Clawmarks — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Clawmarks environment.
Adding a clawmark creates or modifies data (annotations and bookmark metadata) in a reversible manner—clawmarks can be deleted (as evidenced by the delete_clawmark sibling tool) and updated. This is a Write operation, not Execute, because it does not run arbitrary code or trigger external operations; it simply persists annotated metadata to a local JSON file.
From the tool's definition Tool description states it 'Add[s] a clawmark (annotated bookmark)' which creates new data (bookmarks and annotations) in the knowledge graph stored in a local JSON file.
Attacks that exploit this kind of access
Add a clawmark (annotated bookmark) to a location in the code. Clawmarks are points on your trail through the codebase. It is categorised as a Write tool in the Clawmarks MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Clawmarks MCP server in PolicyLayer and add a rule for add_clawmark: 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 Clawmarks. Nothing to install.
add_clawmark 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 add_clawmark 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 add_clawmark. 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.
add_clawmark is provided by the Clawmarks MCP server (mrilikecoding/clawmarks). 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 →