Create a calendar event titled label (default 'Focus') to protect the window.
AI agents use block_focus_time 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.
The tool creates a new calendar event, which is a Write operation (creates data reversibly). Severity is medium because misuse could flood a calendar with unwanted events, disrupting scheduling, but the action is reversible (events can be deleted). It does not execute arbitrary code, delete data irreversibly, or involve financial transactions.
From the tool's definition Tool description states 'Create a calendar event' — this is a create operation that modifies the calendar reversibly by adding an event.
Attacks that exploit this kind of access
Create a calendar event titled label (default 'Focus') to protect the window. 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 block_focus_time: 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.
block_focus_time 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 block_focus_time 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 block_focus_time. 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.
block_focus_time 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 →