查看DolphinDB中，某个库表，其磁盘空间占用
AI agents call query_table_diskusage 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 queries and returns disk usage information for a specified table. It performs a straightforward information retrieval operation with no side effects, no data modification, no code execution, and no destructive capability. The blast radius of misuse is minimal—an attacker could only gain visibility into storage metrics, which does not compromise data integrity or system operations.
From the tool's definition Tool name 'query_table_diskusage' and description '查看DolphinDB中，某个库表，其磁盘空间占用' (view disk space usage of a table in DolphinDB) indicate a read-only query operation that retrieves disk usage metadata without modifying or executing arbitrary operations.
Documented attack patterns abuse exactly the kind of access query_table_diskusage 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 query_table_diskusage:
{
"version": "1",
"default": "deny",
"tools": {
"query_table_diskusage": {}
}
}query_table_diskusage 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 query_table_diskusage: 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.
query_table_diskusage 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 query_table_diskusage 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 query_table_diskusage. 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.
query_table_diskusage 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.