daily_brief
Returns a single morning briefing combining today's calendar events, overdue and due-today reminders, unread inbox email count + subjects, and — when a location is provided — today's weather. Perfect for starting each day: one call gives you everything on your plate.
This record as markdown: /tools/com-local-mcp-local-mcp/daily-brief.md
What daily_brief does on Local
AI agents call daily_brief to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
location | string | — | Optional city name or 'lat,lon' to include today's weather in the brief (e.g. 'London', 'San Francisco'). Omitted if not provided. |
include_emails | boolean | — | Include unread email summary from Mail.app (default true, skipped gracefully if Mail is not running) |
Parameters from the server's own tool schema.
Why daily_brief is rated Low
This tool performs only data retrieval and aggregation across multiple local sources (calendar, reminders, email, weather). It has no side effects, does not modify data, execute code, delete anything, or commit financial obligations. The highest risk would be information disclosure of private calendar/email data, but the tool itself is a read operation with low blast radius if misused by an agent.
From the tool's definition The tool "Returns a single morning briefing" combining "today's calendar events, overdue and due-today reminders, unread inbox email count + subjects, and — when a location is provided — today's weather." These are all read operations that retrieve and…
Attacks that exploit this kind of access
The rule that runs daily_brief safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For daily_brief, this is the rule to start with:
daily_brief is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every daily_brief call is checked against it from then on.
Questions about daily_brief
Returns a single morning briefing combining today's calendar events, overdue and due-today reminders, unread inbox email count + subjects, and — when a location is provided — today's weather. Perfect for starting each day: one call gives you everything on your plate. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
daily_brief accepts 2 parameters: location, include_emails. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for daily_brief: 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 Local. Nothing to install.
daily_brief 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 daily_brief 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 daily_brief. 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.
daily_brief is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue