AI agents call get_calendar to retrieve information from Mcp Sling without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries calendar and shift schedule data for display purposes only. It has no side effects—it does not create, modify, delete records, execute code, or trigger financial transactions. It is a straightforward read operation returning historical or current schedule information.
From the tool's definition Tool name 'get_calendar' and description 'Get calendar information for a specific user in an organization. Returns schedule and shift data for the specified date range.' indicate data retrieval with no modification, deletion, or execution of external actions.
Attacks that exploit this kind of access
Get calendar information for a specific user in an organization. Returns schedule and shift data for the specified date range. It is categorised as a Read tool in the Mcp Sling MCP Server, which means it retrieves data without modifying state.
Register the Mcp Sling MCP server in PolicyLayer and add a rule for get_calendar: 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 Mcp Sling. Nothing to install.
get_calendar 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 get_calendar 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 get_calendar. 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.
get_calendar is provided by the Mcp Sling MCP server (poncheck/mcp-sling). 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 →