list_calendars

The project's calendars, each with its sources of events and their ids (for update_calendar)

SERVERQuintaDB SOURCEhttps://quintadb.com/mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-quintadb-mcp/list-calendars.md

WHAT IT DOES

What list_calendars does on QuintaDB

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

Parameter	Type	Required	Description
`app_id`	string	Yes	Project ID (from list_projects)

Parameters from the server's own tool schema.

RISK

Why list_calendars is rated Low

Even though list_calendars only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_calendars safely

PolicyLayer is an MCP gateway: it sits between your AI agents and QuintaDB, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_calendars, this is the rule to start with:

list_calendars Allowed

list_calendars is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_calendars": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect QuintaDB, apply this rule, and every list_calendars call is checked against it from then on.

FAQ

Questions about list_calendars

What does the list_calendars tool do? +

The project's calendars, each with its sources of events and their ids (for update_calendar). It is categorised as a Read tool in the QuintaDB MCP Server, which means it retrieves data without modifying state.

What parameters does list_calendars accept? +

list_calendars accepts 1 parameter: app_id. Required: app_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_calendars? +

Register the QuintaDB MCP server in PolicyLayer and add a rule for list_calendars: 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 QuintaDB. Nothing to install.

What risk level is list_calendars? +

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

Can I rate-limit list_calendars? +

Yes. Add a rate_limit block to the list_calendars 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 list_calendars completely? +

Set action: deny in the PolicyLayer policy for list_calendars. 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 list_calendars? +

list_calendars is provided by the QuintaDB MCP server (https://quintadb.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on QuintaDB, and thousands of servers like it.

This server

All 150 QuintaDB tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →