AI agents call get_calendar to retrieve information from Legal without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and retrieves calendar data from the Clio practice management system. It has no side effects—it does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal; an AI agent accessing calendar entries could at worst read sensitive scheduling information, but cannot alter deadlines, create false entries, or trigger external actions.
From the tool's definition Tool retrieves calendar entries (hearings, deadlines, meetings) from Clio. The description uses 'get' and 'retrieve' language with no modification, creation, or deletion operations mentioned.
Attacks that exploit this kind of access
Get calendar entries (hearings, deadlines, meetings) from Clio. It is categorised as a Read tool in the Legal MCP Server, which means it retrieves data without modifying state.
Register the Legal 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 Legal. 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 Legal MCP server (jscottym/legal-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 →