get_reminder_preferences

Get local reminder preferences (due-soon window, SLA warning lead, desktop notify).

SERVERTodos SOURCE@hasna/todos

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/todos/get-reminder-preferences.md

WHAT IT DOES

What get_reminder_preferences does on Todos

AI agents call get_reminder_preferences to retrieve information from Todos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_reminder_preferences is rated Low

This tool retrieves user preferences for reminders without side effects. It performs a read operation on stored configuration data. No data is created, modified, deleted, or executed. The low severity reflects that preference data is non-sensitive and read-only access poses minimal risk.

From the tool's definition Tool name and description indicate retrieval only: 'Get local reminder preferences' with parameters (due-soon window, SLA warning lead, desktop notify) are all configuration settings being queried, not modified or executed.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_reminder_preferences safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Todos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_reminder_preferences, this is the rule to start with:

get_reminder_preferences Allowed

get_reminder_preferences is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Todos, apply this rule, and every get_reminder_preferences call is checked against it from then on.

FAQ

Questions about get_reminder_preferences

What does the get_reminder_preferences tool do? +

Get local reminder preferences (due-soon window, SLA warning lead, desktop notify). It is categorised as a Read tool in the Todos MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_reminder_preferences? +

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

What risk level is get_reminder_preferences? +

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

Can I rate-limit get_reminder_preferences? +

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

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

get_reminder_preferences is provided by the Todos MCP server (@hasna/todos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Todos, and thousands of servers like it.

This server

All 528 Todos tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →