custom_name · Cryptosense MCP: Risk & Policy

WHAT IT DOES

What custom_name does on Cryptosense

AI agents call custom_name as a supporting operation in Cryptosense workflows.

WHY IT NEEDS A POLICY

Why custom_name needs a policy

With an empty description and a non-descriptive name, there is no basis for classification. The server context (crypto market intelligence) does not clearly indicate what 'custom_name' does. Confidence is very low; defaulting to Other with low severity.

From the tool's definition Tool name is 'custom_name' and description is empty. No information available to determine what this tool does.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

custom_name Rate-limited

custom_name gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "custom_name": {
      "limits": [
        {
          "counter": "custom_name_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Cryptosense, so you can run agents against it safely.

FAQ

Questions about custom_name

What does the custom_name tool do? +

custom_name. It is categorised as a Other tool in the Cryptosense MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on custom_name? +

Register the Cryptosense MCP server in PolicyLayer and add a rule for custom_name: 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 custom_name? +

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

Can I rate-limit custom_name? +

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

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

custom_name 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.