Check if the Cal.com API key is configured in the environment.
AI agents call get_api_status to retrieve information from Cal Com MCP Server for Customers without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves configuration status information without creating, modifying, deleting, or executing any operations. It is a simple diagnostic query that does not alter state or trigger external actions. The blast radius of misuse is minimal—an agent could only learn whether an API key is configured, which is low-sensitivity operational metadata.
From the tool's definition Tool name 'get_api_status' and description 'Check if the Cal.com API key is configured' indicate a read-only status check operation with no side effects.
Attacks that exploit this kind of access
Check if the Cal.com API key is configured in the environment. It is categorised as a Read tool in the Cal Com MCP Server for Customers MCP Server, which means it retrieves data without modifying state.
Register the Cal Com MCP Server for Customers MCP server in PolicyLayer and add a rule for get_api_status: 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 Cal Com MCP Server for Customers. Nothing to install.
get_api_status 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_api_status 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_api_status. 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_api_status is provided by the Cal Com MCP Server for Customers MCP server (niopub/calcom-mcp-for-customers). 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 →