view_meeting_schedules
AI agents call view_meeting_schedules to retrieve information from Schedulia MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves calendar/schedule information for display purposes. The verb 'view' and the context of a scheduling assistant confirm this is a data retrieval operation with no capability to modify, delete, or execute actions. Low severity because unauthorized access reveals calendar availability but not typically high-sensitivity data, and misuse would require already having system access.
From the tool's definition Tool name 'view_meeting_schedules' indicates viewing/querying schedule data with no modifications. Server description states it 'enables users to view schedules' as a core read-only function.
Attacks that exploit this kind of access
view_meeting_schedules. It is categorised as a Read tool in the Schedulia MCP MCP Server, which means it retrieves data without modifying state.
Register the Schedulia MCP server in PolicyLayer and add a rule for view_meeting_schedules: 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 Schedulia MCP. Nothing to install.
view_meeting_schedules 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 view_meeting_schedules 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 view_meeting_schedules. 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.
view_meeting_schedules is provided by the Schedulia MCP server (watanka/schedulia-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 →