Rename a tag across all notes in your Bear library. Useful for reorganizing tag taxonomy, fixing typos, or restructuring tag hierarchies. Use bear-list-tags first to see existing tags.
AI agents use bear-rename-tag 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.
This tool modifies existing data (tags) across multiple notes in a reversible manner. It updates tag names throughout the library but does not delete data or execute arbitrary code. The operation is reversible—tags can be renamed back to their original names. While it affects multiple notes, the change is scoped to tag renaming and does not constitute destructive deletion.
From the tool's definition Rename a tag across all notes in your Bear library
Documented attack patterns abuse exactly the kind of access bear-rename-tag 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-rename-tag:
{
"version": "1",
"default": "deny",
"tools": {
"bear-rename-tag": {
"limits": [
{
"counter": "bear-rename-tag_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}bear-rename-tag 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.
Rename a tag across all notes in your Bear library. Useful for reorganizing tag taxonomy, fixing typos, or restructuring tag hierarchies. Use bear-list-tags first to see existing tags. 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-rename-tag: 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-rename-tag 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-rename-tag 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-rename-tag. 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-rename-tag 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.