Search entries already saved in the local SQLite cache.
AI agents call search_cached_entries to retrieve information from LiveJournal MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a local cache database and returns matching results. It performs no writes, deletions, code execution, or financial operations. The blast radius of misuse is minimal since it can only expose data already present in the cache to which the user has legitimate access. Confidence is high because the description clearly delineates the function as search-only with no modification semantics.
From the tool's definition Tool description states 'Search entries already saved in the local SQLite cache' — a query operation with no side effects. The verb 'search' and scope 'cached entries' indicate data retrieval only.
Attacks that exploit this kind of access
Search entries already saved in the local SQLite cache. It is categorised as a Read tool in the LiveJournal MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LiveJournal MCP Server MCP server in PolicyLayer and add a rule for search_cached_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 LiveJournal MCP Server. Nothing to install.
search_cached_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_cached_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_cached_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_cached_entries is provided by the LiveJournal MCP Server MCP server (pavelber/livejournal-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 →