Search and filter journal entries
AI agents call search_entries to retrieve information from jrnl MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries journal entry data without creating, modifying, deleting, or executing external operations. It has no side effects beyond returning results. The low severity reflects minimal risk even if misused—an AI agent searching entries cannot cause harm beyond potentially accessing sensitive personal journal content.
From the tool's definition Tool name 'search_entries' and description 'Search and filter journal entries' indicate data retrieval with no modification.
Attacks that exploit this kind of access
Search and filter journal entries. It is categorised as a Read tool in the jrnl MCP Server MCP Server, which means it retrieves data without modifying state.
Register the jrnl MCP Server MCP server in PolicyLayer and add a rule for search_entries: 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 jrnl MCP Server. Nothing to install.
search_entries 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 search_entries 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 search_entries. 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.
search_entries is provided by the jrnl MCP Server MCP server (yostos/jrnl-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 →