Send a message to any AI model via Crazyrouter. Supports 627+ models including GPT-5, Claude Opus 4.6, Gemini 3, DeepSeek R1, Llama 4, Qwen3, Grok 4, and more.
AI agents invoke chat to trigger actions in Crazyrouter. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers external API calls to third-party AI models, which constitutes executing an external operation with effects dependent on the arguments (model choice, message content). While it primarily retrieves a response, it consumes API credits/quota, may have downstream side effects depending on the model used, and routes arbitrary prompts to powerful external systems.
From the tool's definition "Send a message to any AI model via Crazyrouter" and "Supports 627+ models including GPT-5, Claude Opus 4.6, Gemini 3..."
Attacks that exploit this kind of access
Send a message to any AI model via Crazyrouter. Supports 627+ models including GPT-5, Claude Opus 4.6, Gemini 3, DeepSeek R1, Llama 4, Qwen3, Grok 4, and more. It is categorised as a Execute tool in the Crazyrouter MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Crazyrouter MCP server in PolicyLayer and add a rule for chat: 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 Crazyrouter. Nothing to install.
chat is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the chat 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 chat. 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.
chat is provided by the Crazyrouter MCP server (xujfcn/crazyrouter-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
chat is one line of Crazyrouter'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 →