AI agents use archive_note to create or update resources in MCP Bear — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Bear environment.
Archiving a note changes its state/metadata but does not permanently delete data—the note remains accessible in an archived state and can be unarchived. This is a Write operation rather than Destructive. The severity is medium because misuse could hide important information or disrupt user workflows, but the action is reversible and does not result in data loss.
From the tool's definition The tool 'archive_note' modifies the state of a note by archiving it. This is a reversible data modification action, distinct from deletion. The server description confirms it provides 'write access to Bear Notes' and mentions the ability to 'archive' notes.
Attacks that exploit this kind of access
Archive a note. It is categorised as a Write tool in the MCP Bear MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Bear MCP server in PolicyLayer and add a rule for 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 MCP Bear. Nothing to install.
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 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 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.
archive_note is provided by the MCP Bear MCP server (maxim-ist/mcp-bear). 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 →