morning_brief
Get your daily morning intelligence brief. Delivers top priorities, overnight signals, pipeline health, calendar prep, and coaching — all in 30 seconds. Automatically adapts to your role (SDR/AE/VP). Cached per day so it runs fast on repeat calls. This is the first thing to check every morning.
This record as markdown: /tools/adrata-starfield-mcp/morning-brief.md
What morning_brief does on Starfield
AI agents call morning_brief to retrieve information from Starfield 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 |
|---|---|---|---|
force_refresh | boolean | — | Force regeneration even if already delivered today (default: false) |
role_override | string | — | Override auto-detected role for brief focus (default: auto-detect from profile) |
Parameters from the server's own tool schema.
Why morning_brief is rated Low
Even though morning_brief only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs morning_brief safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Starfield, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For morning_brief, this is the rule to start with:
morning_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 Starfield, apply this rule, and every morning_brief call is checked against it from then on.
Questions about morning_brief
Get your daily morning intelligence brief. Delivers top priorities, overnight signals, pipeline health, calendar prep, and coaching — all in 30 seconds. Automatically adapts to your role (SDR/AE/VP). Cached per day so it runs fast on repeat calls. This is the first thing to check every morning. It is categorised as a Read tool in the Starfield MCP Server, which means it retrieves data without modifying state.
morning_brief accepts 2 parameters: force_refresh, role_override. The full parameter table on this page comes from the server's own tool schema.
Register the Starfield MCP server in PolicyLayer and add a rule for morning_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 Starfield. Nothing to install.
morning_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 morning_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 morning_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.
morning_brief is provided by the Starfield MCP server (@adrata/starfield-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Starfield, and thousands of servers like it.
This server
Across the catalogue