AI agents call find_meeting_slot to retrieve information from Meridian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a timezone calculation and lookup operation to identify available meeting times. It queries data (participant timezones, working hours, date) and returns recommendations. No side effects occur—it does not create calendar entries, execute commands, delete data, or transfer funds. This is characteristic of a Read category tool: data retrieval with informational output only.
From the tool's definition Tool 'find_meeting_slot' returns suggested meeting times based on timezone and working-hour data. Description indicates it 'finds overlapping working-hour slots' and 'suggests' a meeting slot—purely informational operations with no modification, deletion,…
Attacks that exploit this kind of access
Find the overlapping working-hour window for a set of participants in different timezones on a given date, and suggest a meeting slot of the requested duration. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
Register the Meridian MCP server in PolicyLayer and add a rule for find_meeting_slot: 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 Meridian. Nothing to install.
find_meeting_slot 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_meeting_slot 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_meeting_slot. 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_meeting_slot is provided by the Meridian MCP server (marcusicaro/meridian-mcp). 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 →