Low Risk

get_calendar

Get calendar entries (hearings, deadlines, meetings) from Clio.

How to control get_calendar ↓

What get_calendar does on LegalMCP

AI agents call get_calendar to retrieve information from LegalMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_calendar needs a policy

This tool only retrieves existing calendar data from Clio practice management system. It has no side effects, does not modify or delete data, does not execute operations, and does not involve financial transactions. The read-only nature is clear from both the 'get_' prefix and the descriptive language indicating data retrieval.

From the tool's definition Tool is named 'get_calendar' with description stating it retrieves 'calendar entries (hearings, deadlines, meetings) from Clio' — uses 'get' verb and explicitly describes retrieval/read operations with no modification, deletion, or execution described.

Documented attack patterns abuse exactly the kind of access get_calendar gives an agent:

How to control get_calendar

PolicyLayer is an MCP gateway — it sits between your AI agents and LegalMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_calendar:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_calendar": {}
  }
}

get_calendar is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register LegalMCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_calendar

What does the get_calendar tool do? +

Get calendar entries (hearings, deadlines, meetings) from Clio. It is categorised as a Read tool in the LegalMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_calendar? +

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 LegalMCP. Nothing to install.

What risk level is get_calendar? +

get_calendar is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_calendar? +

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.

How do I block get_calendar completely? +

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.

What MCP server provides get_calendar? +

get_calendar is provided by the Legal MCP server (mahender22/legal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every LegalMCP tool call.

Start from LegalMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

18 LegalMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.