pipedrive_get_current_user
Get details of the current user (API key owner). Useful for verifying connection and getting your user ID.
This record as markdown: /tools/ckalima-pipedrive-mcp-server/pipedrive-get-current-user.md
What pipedrive_get_current_user does on Pipedrive MCP Server
AI agents call pipedrive_get_current_user to retrieve information from Pipedrive MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why pipedrive_get_current_user is rated Low
This tool only retrieves authentication context information about the API key owner. It performs no modifications, deletions, or external operations. The low severity reflects that user profile metadata is generally non-sensitive in CRM systems and the blast radius of misuse is minimal. High confidence due to clear, explicit description indicating read-only behavior.
From the tool's definition Tool description states 'Get details of the current user' and is explicitly for 'verifying connection and getting your user ID' — a read-only retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs pipedrive_get_current_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pipedrive MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pipedrive_get_current_user, this is the rule to start with:
pipedrive_get_current_user is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Pipedrive MCP Server, apply this rule, and every pipedrive_get_current_user call is checked against it from then on.
Questions about pipedrive_get_current_user
Get details of the current user (API key owner). Useful for verifying connection and getting your user ID. It is categorised as a Read tool in the Pipedrive MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Pipedrive MCP Server MCP server in PolicyLayer and add a rule for pipedrive_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 Pipedrive MCP Server. Nothing to install.
pipedrive_get_current_user 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 pipedrive_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.
Set action: deny in the PolicyLayer policy for pipedrive_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.
pipedrive_get_current_user is provided by the Pipedrive MCP Server MCP server (ckalima/pipedrive-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pipedrive MCP Server, and thousands of servers like it.
This server
Across the catalogue