Find slots of duration_minutes between [start, end]. working_hours = [start_hour, end_hour], default [9,18].
AI agents call find_free_time to retrieve information from Nexus Core without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries scheduling data to identify available time slots. It performs a search or lookup operation with no side effects—it does not create, modify, delete, execute commands, or affect financial state. The parameters (duration_minutes, start, end, working_hours) are all inputs that filter a read operation.
From the tool's definition Tool is named 'find_free_time' and described as finding 'slots of duration_minutes between [start, end]' with optional working_hours parameters.
Attacks that exploit this kind of access
Find slots of duration_minutes between [start, end]. working_hours = [start_hour, end_hour], default [9,18]. It is categorised as a Read tool in the Nexus Core MCP Server, which means it retrieves data without modifying state.
Register the Nexus Core MCP server in PolicyLayer and add a rule for find_free_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.
find_free_time 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 find_free_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 find_free_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.
find_free_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 →