从数据库导入数据到Excel文件 Args: db_connection_string: 数据库连接字符串 query: SQL查询语句 output_file: 输出Excel文件名，默认为query_result.xlsx Returns: 包含操作结果的字典
AI agents use import_database_to_excel to create or update resources in Office Editor — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Office Editor environment.
The tool writes/creates data into an Excel file by executing an arbitrary SQL query against a database connection. While it executes a query (Execute-class behavior), the primary effect is writing results to a new or modified file, making it Write category.
From the tool's definition Tool performs 'import_database_to_excel' with parameters 'db_connection_string', 'query' (SQL execution), and 'output_file'. Creates or modifies Excel file with imported data. Description states '从数据库导入数据到Excel文件' (import data from database to Excel file).
Documented attack patterns abuse exactly the kind of access import_database_to_excel gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Office Editor, and nothing reaches the server without passing your rules. This is the rule we recommend for import_database_to_excel:
{
"version": "1",
"default": "deny",
"tools": {
"import_database_to_excel": {
"limits": [
{
"counter": "import_database_to_excel_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}import_database_to_excel stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
从数据库导入数据到Excel文件 Args: db_connection_string: 数据库连接字符串 query: SQL查询语句 output_file: 输出Excel文件名，默认为query_result.xlsx Returns: 包含操作结果的字典. It is categorised as a Write tool in the Office Editor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Office Editor MCP server in PolicyLayer and add a rule for import_database_to_excel: 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 Office Editor. Nothing to install.
import_database_to_excel is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the import_database_to_excel 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 import_database_to_excel. 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.
import_database_to_excel is provided by the Office Editor MCP server (thewdy/office-editor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 88 Office Editor tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
88 Office Editor tools catalogued and risk-classified — across an index of 42,500+ MCP servers.