tool_with_context · Cryptosense MCP: Risk & Policy

WHAT IT DOES

What tool_with_context does on Cryptosense

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

WHY IT NEEDS A POLICY

Why tool_with_context needs a policy

With no description and a generic name, there is insufficient information to classify this tool into a meaningful risk category. The server context (crypto market intelligence) and sibling tools don't provide enough signal to infer what this specific tool does. Confidence is very low.

From the tool's definition Tool name is 'tool_with_context' and description is empty/uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tool_with_context Rate-limited

tool_with_context 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": {
    "tool_with_context": {
      "limits": [
        {
          "counter": "tool_with_context_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 tool_with_context

What does the tool_with_context tool do? +

tool_with_context. 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 tool_with_context? +

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

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

Can I rate-limit tool_with_context? +

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

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

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

// THE FULL RECORD

tool_with_context is one line of Cryptosense's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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