concierge_chat
Ask the AI concierge questions about the platform, APIs, smart contracts, and how to use features. No api_key required.
This record as markdown: /tools/io-github-wirternow-agent-bank/concierge-chat.md
What concierge_chat does on Ai Agent Bank
AI agents call concierge_chat to retrieve information from Ai Agent Bank without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
message | string | Yes | Question or message for the concierge |
agent_id | string | — | Optional agent UUID for context |
Parameters from the server's own tool schema.
Why concierge_chat is rated Low
The concierge_chat tool functions as a question-answering interface that provides guidance and information about the platform. It does not create wallets, transfer funds, execute trades, delete data, or trigger any irreversible or financial actions. The lack of api_key requirement further indicates it is a read-only informational service.
From the tool's definition The tool is described as 'Ask the AI concierge questions about the platform, APIs, smart contracts, and how to use features.' This is purely informational—it retrieves documentation and explanatory information without executing transactions, modifying data,…
Attacks that exploit this kind of access
The rule that runs concierge_chat safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ai Agent Bank, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For concierge_chat, this is the rule to start with:
concierge_chat is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ai Agent Bank, apply this rule, and every concierge_chat call is checked against it from then on.
Questions about concierge_chat
Ask the AI concierge questions about the platform, APIs, smart contracts, and how to use features. No api_key required. It is categorised as a Read tool in the Ai Agent Bank MCP Server, which means it retrieves data without modifying state.
concierge_chat accepts 2 parameters: message, agent_id. Required: message. The full parameter table on this page comes from the server's own tool schema.
Register the Ai Agent Bank MCP server in PolicyLayer and add a rule for concierge_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 Ai Agent Bank. Nothing to install.
concierge_chat is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the concierge_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 concierge_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.
concierge_chat is provided by the Ai Agent Bank MCP server (https://tdueqhfxyojmjgactdyc.supabase.co/functions/v1/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ai Agent Bank, and thousands of servers like it.
This server
Across the catalogue