get_user_id

A read tool on the Cryptosense MCP server.

SERVERCryptosense SOURCEjosephibra/cryptosense-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/josephibra-cryptosense-mcp/get-user-id.md

WHAT IT DOES

What get_user_id does on Cryptosense

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

RISK

Why get_user_id is rated Low

The tool appears to retrieve or query user identity information with no apparent side effects. While the empty description reduces confidence slightly, the naming convention strongly suggests a Read operation. Even if this retrieves user context for subsequent operations, retrieval itself is non-destructive and fits the Read category.

From the tool's definition Tool name 'get_user_id' indicates retrieval of a user identifier. No description provided to suggest write, delete, execute, or financial operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_user_id safely

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

get_user_id Allowed

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

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

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

FAQ

Questions about get_user_id

What does the get_user_id tool do? +

get_user_id is a read tool on the Cryptosense MCP server. It is categorised as a Read tool in the Cryptosense MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_user_id? +

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

What risk level is get_user_id? +

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

Can I rate-limit get_user_id? +

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

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

get_user_id is provided by the Cryptosense MCP server (josephibra/cryptosense-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Cryptosense, and thousands of servers like it.

This server

All 36 Cryptosense 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 →