calendly_get_current_user

Get the current Calendly user

SERVERScopeGate SOURCEhttps://mcp.scopegate.cloud/{api_key}
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/io-github-alifanov-scopegate/calendly-get-current-user.md

What calendly_get_current_user does on ScopeGate

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

Why calendly_get_current_user is rated Low

This tool retrieves information about the authenticated user with no side effects, no data modification, and no external operations triggered. It is purely a read operation to fetch user details. Severity is low because the blast radius of misuse is limited to exposure of the authenticated user's own identity information, which is typically non-sensitive and often already known to the agent making the request.

From the tool's definition Tool name 'calendly_get_current_user' and description 'Get the current Calendly user' indicate a retrieval operation that queries user identity/profile information without modification.

Questions about calendly_get_current_user

What does the calendly_get_current_user tool do? +

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

How do I enforce a policy on calendly_get_current_user? +

Register the ScopeGate 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 ScopeGate. 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 ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on ScopeGate, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of ScopeGate's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.