Show notes with specific tag(s)
AI agents call open_tag to retrieve information from Bear MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool only shows/displays notes associated with specific tags in Bear. This is a read-only retrieval operation with no side effects or data modification.
From the tool's definition "Show notes with specific tag(s)" — purely displays/retrieves notes filtered by tag, no modification
Attacks that exploit this kind of access
Show notes with specific tag(s). It is categorised as a Read tool in the Bear MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bear MCP Server MCP server in PolicyLayer and add a rule for open_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 MCP Server. Nothing to install.
open_tag is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the open_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 open_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.
open_tag is provided by the Bear MCP Server MCP server (philgetzen/bear-mcp). 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 →