Lists calendar entries within a date range. Use ISO dates (YYYY-MM-DD).
AI agents call clio_list_calendar_entries to retrieve information from Clio Manage MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns calendar data without creating, modifying, deleting, or executing any operations. The verb 'Lists' is explicitly a read-only operation. The severity is low because exposure of calendar metadata poses minimal direct harm—it reveals scheduling information but does not affect financial systems, enable destructive actions, or execute external code.
From the tool's definition Tool name 'clio_list_calendar_entries' and description 'Lists calendar entries within a date range' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Lists calendar entries within a date range. Use ISO dates (YYYY-MM-DD). It is categorised as a Read tool in the Clio Manage MCP MCP Server, which means it retrieves data without modifying state.
Register the Clio Manage MCP server in PolicyLayer and add a rule for clio_list_calendar_entries: 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 Clio Manage MCP. Nothing to install.
clio_list_calendar_entries 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 clio_list_calendar_entries 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 clio_list_calendar_entries. 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.
clio_list_calendar_entries is provided by the Clio Manage MCP server (patrickking67/clio-manage-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 →