AI agents call list_tbs to retrieve information from Dolphindb without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about tables within a DolphinDB database—a read-only query operation. It has no side effects, cannot modify data, execute code, or cause irreversible changes. The blast radius of misuse is minimal; an agent could at worst enumerate database schema, which is informational only.
From the tool's definition Tool name 'list_tbs' and description '查看 DolphinDB中,某个分布式库下面有哪些表' (View which tables exist in a distributed database in DolphinDB) indicate a listing/inspection operation with no data modification or execution.
Documented attack patterns abuse exactly the kind of access list_tbs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Dolphindb, and nothing reaches the server without passing your rules. This is the rule we recommend for list_tbs:
{
"version": "1",
"default": "deny",
"tools": {
"list_tbs": {}
}
} list_tbs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
查看 DolphinDB中,某个分布式库下面有哪些表. It is categorised as a Read tool in the Dolphindb MCP Server, which means it retrieves data without modifying state.
Register the Dolphindb MCP server in PolicyLayer and add a rule for list_tbs: 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 Dolphindb. Nothing to install.
list_tbs 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 list_tbs 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 list_tbs. 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.
list_tbs is provided by the Dolphindb MCP server (tradercjz/dolphindb-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Dolphindb, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 Dolphindb tools catalogued and risk-classified — across an index of 43,000+ MCP servers.