AI agents use bear-archive-note to create or update resources in Bear Notes — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bear Notes environment.
Archiving a note modifies its status/location reversibly—notes can be unarchived. This is a write operation (state change) rather than destructive (irreversible deletion). While it affects note organization, the data remains intact and recoverable, warranting 'medium' severity due to potential workflow disruption if misapplied, but not 'high' since the action is reversible.
From the tool's definition Tool name 'bear-archive-note' and description 'Move a note to Bear' indicate modification of note state/location within the Bear app. This changes where a note is stored but does not delete or destroy data.
Documented attack patterns abuse exactly the kind of access bear-archive-note gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bear Notes, and nothing reaches the server without passing your rules. This is the rule we recommend for bear-archive-note:
{
"version": "1",
"default": "deny",
"tools": {
"bear-archive-note": {
"limits": [
{
"counter": "bear-archive-note_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}bear-archive-note 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.
Move a note to Bear. It is categorised as a Write tool in the Bear Notes MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bear Notes MCP server in PolicyLayer and add a rule for bear-archive-note: 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 Bear Notes. Nothing to install.
bear-archive-note 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 bear-archive-note 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 bear-archive-note. 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.
bear-archive-note is provided by the Bear Notes MCP server (vasylenko/bear-notes-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 Bear Notes tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 Bear Notes tools catalogued and risk-classified — across an index of 42,500+ MCP servers.