ask_assistant
AI crypto trading assistant — ask any market question, grounded in live data. $0.10
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/ask-assistant.md
What ask_assistant does on Crypto Intelligence
AI agents use ask_assistant to commit financial operations through Crypto Intelligence, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
message | string | Yes | Your question about crypto markets |
portfolio | string | — | Comma-separated coin list (e.g. BTC,ETH,SOL) |
risk_tolerance | string | — | Risk level: low, medium, high |
Parameters from the server's own tool schema.
Why ask_assistant is rated Critical
Each invocation triggers a $0.10 micropayment via x402, making this a Financial category tool. While the tool itself only retrieves/answers market questions (Read-like behavior), every call incurs a real financial transaction. Under the severity rules, Financial > all other categories. Severity is high because an AI agent could invoke this tool many times autonomously, accumulating significant charges.
From the tool's definition 'AI crypto trading assistant', '$0.10' micropayment cost per call, 'x402 micropayments' in server description
Attacks that exploit this kind of access
The rule that runs ask_assistant safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crypto Intelligence, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ask_assistant, this is the rule to start with:
Any call to ask_assistant is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Crypto Intelligence, apply this rule, and every ask_assistant call is checked against it from then on.
Questions about ask_assistant
AI crypto trading assistant — ask any market question, grounded in live data. $0.10. It is categorised as a Financial tool in the Crypto Intelligence MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
ask_assistant accepts 3 parameters: message, portfolio, risk_tolerance. Required: message. The full parameter table on this page comes from the server's own tool schema.
Register the Crypto Intelligence MCP server in PolicyLayer and add a rule for ask_assistant: 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 Crypto Intelligence. Nothing to install.
ask_assistant is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the ask_assistant 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 ask_assistant. 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.
ask_assistant is provided by the Crypto Intelligence MCP server (https://api.carbon-cashmere.de/mcp/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crypto Intelligence, and thousands of servers like it.
Across the catalogue