Find available time slots in a range.
AI agents call calendar_find_free_slots to retrieve information from AIOS Co-Founder MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries calendar data to identify free time slots. It performs a read-only retrieval of availability information with no side effects, no data modification, no code execution, and no financial impact. The low severity reflects minimal risk even if misused by an agent, as the worst outcome would be information disclosure about calendar availability.
From the tool's definition Tool name is 'calendar_find_free_slots' and description states it 'Find[s] available time slots in a range' — a query operation that retrieves calendar availability data without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Find available time slots in a range. It is categorised as a Read tool in the AIOS Co-Founder MCP MCP Server, which means it retrieves data without modifying state.
Register the AIOS Co-Founder MCP server in PolicyLayer and add a rule for calendar_find_free_slots: 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 AIOS Co-Founder MCP. Nothing to install.
calendar_find_free_slots 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 calendar_find_free_slots 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 calendar_find_free_slots. 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.
calendar_find_free_slots is provided by the AIOS Co-Founder MCP server (varun-b-nagaraj/python-mcp-server). 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 →