Create a reminder. fire_at = ISO-8601 datetime. recurring optional (e.g. 'FREQ=DAILY').
AI agents use create_reminder to create or update resources in Nexus Core — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nexus Core environment.
This tool creates a new reminder entry in the system, which is a reversible write operation. It does not delete, execute arbitrary code, move money, or have destructive side effects. The blast radius is minimal—a mistaken reminder is easily deleted or ignored. Severity is low because reminder creation is benign even if misdirected by an agent.
From the tool's definition Tool name is 'create_reminder' and description states it creates a reminder with fire_at (datetime) and optional recurring parameters. The verb 'create' indicates data creation.
Attacks that exploit this kind of access
Create a reminder. fire_at = ISO-8601 datetime. recurring optional (e.g. 'FREQ=DAILY'). It is categorised as a Write tool in the Nexus Core MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nexus Core MCP server in PolicyLayer and add a rule for create_reminder: 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 Nexus Core. Nothing to install.
create_reminder is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_reminder 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 create_reminder. 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.
create_reminder is provided by the Nexus Core MCP server (noumenon-ai/nexus-core). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →