weekly_review

Sunday-flavored weekly digest: journal entries logged this week, house projects that moved, workouts completed, gifts given/bought, and what

Server Personal Brain phantomts/personal-brain-mcp
Category Read
Risk class Low
Parameters 00 required

What weekly_review does on Personal Brain

AI agents call weekly_review to retrieve information from Personal Brain without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why weekly_review needs a policy

The weekly_review tool compiles a summary of existing personal data across multiple domains (journals, home projects, fitness, gifts). It performs semantic retrieval and aggregation only; the description contains no verbs indicating creation, modification, deletion, or execution of external operations. The incomplete description ('and what') suggests informational retrieval.

From the tool's definition Tool retrieves and aggregates weekly digest data including 'journal entries logged this week, house projects that moved, workouts completed, gifts given/bought' — all query/retrieval operations with no modification or side effects.

Questions about weekly_review

What does the weekly_review tool do? +

Sunday-flavored weekly digest: journal entries logged this week, house projects that moved, workouts completed, gifts given/bought, and what. It is categorised as a Read tool in the Personal Brain MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on weekly_review? +

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

What risk level is weekly_review? +

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

Can I rate-limit weekly_review? +

Yes. Add a rate_limit block to the weekly_review 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 weekly_review completely? +

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

weekly_review is provided by the Personal Brain MCP server (phantomts/personal-brain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.