AI agents use unarchive_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.
Unarchiving a note is a reversible modification operation that changes note status/metadata without permanently deleting data. It qualifies as Write rather than Destructive because the action can be undone (re-archiving), and it does not irreversibly delete or overwrite data.
From the tool's definition Tool description states 'Unarchive a note', which restores a note to active status. The server uses 'x-callback-url for modifications' per the server description, indicating this performs a state change via Bear's callback interface.
Attacks that exploit this kind of access
Unarchive 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 unarchive_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.
unarchive_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 unarchive_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 unarchive_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.
unarchive_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 →