calendly_get_current_user

Get the current authenticated Calendly user.

SERVERIntegrations MCP SOURCEshriram-vasudevan/integrations-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/shriram-vasudevan-integrations-mcp/calendly-get-current-user.md

WHAT IT DOES

What calendly_get_current_user does on Integrations MCP

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

RISK

Why calendly_get_current_user is rated Low

This tool queries user profile data and returns information about the authenticated user without creating, modifying, deleting, or executing any operations. It is a straightforward read operation. The blast radius of misuse is minimal—an AI agent could only retrieve user metadata, which has low impact.

From the tool's definition Tool name and description indicate retrieval of current user information: 'Get the current authenticated Calendly user' — a simple read operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs calendly_get_current_user safely

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

calendly_get_current_user Allowed

calendly_get_current_user 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": {
    "calendly_get_current_user": {}
  }
}

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

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

FAQ

Questions about calendly_get_current_user

What does the calendly_get_current_user tool do? +

Get the current authenticated Calendly user. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on calendly_get_current_user? +

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

What risk level is calendly_get_current_user? +

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

Can I rate-limit calendly_get_current_user? +

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

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

calendly_get_current_user is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Integrations, and thousands of servers like it.

This server

All 420 Integrations tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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