get_entry_count

THE RISK

Low Risk

Why get_entry_count needs a policy

This tool retrieves metadata (a count) from a journal without creating, modifying, deleting, or executing any operations. It is a safe read-only query with minimal blast radius if invoked by an AI agent.

From the tool's definition Tool name 'get_entry_count' and description 'Get the total number of entries in a journal' indicate a query operation that retrieves aggregate data without modification or side effects.

Documented attack patterns abuse exactly the kind of access get_entry_count gives an agent:

POLICY

How to control get_entry_count

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-DayOne, and nothing reaches the server without passing your rules. This is the rule we recommend for get_entry_count:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_entry_count": {}
  }
}

get_entry_count is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register MCP-DayOne — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP-DayOne tools

Write create_entry_with_attachments Create a journal entry with file attachments (photos, videos, audio, PDFs) Write create_journal_entry Create a new entry in Day One journal with support for attachments, location, and metadata Write create_location_entry Create a journal entry with location coordinates Read get_entries_by_date Get journal entries for a specific date across multiple years ( Read get_entry_count_from_db Get actual entry count from Day One database Read list_journals List all available Day One journals Read list_journals_from_db List all journals from database with entry counts Read read_recent_entries Read recent journal entries from Day One database

All 10 MCP-DayOne tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_entry_count

What does the get_entry_count tool do? +

Get the total number of entries in a journal. It is categorised as a Read tool in the MCP-DayOne MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_entry_count? +

Register the MCP-DayOne MCP server in PolicyLayer and add a rule for get_entry_count: 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-DayOne. Nothing to install.

What risk level is get_entry_count? +

get_entry_count is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_entry_count? +

Yes. Add a rate_limit block to the get_entry_count 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.

How do I block get_entry_count completely? +

Set action: deny in the PolicyLayer policy for get_entry_count. 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.

What MCP server provides get_entry_count? +

get_entry_count is provided by the MCP-DayOne MCP server (quevin/mcp-dayone). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP-DayOne tool call.

Start from MCP-DayOne, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →