定时生成 Excel 报表.
AI agents invoke schedule_excel_report_generation to trigger actions in Office MCP Server. 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 schedules and triggers automated Excel report generation at specified times, which constitutes executing an external operation/automation task rather than simply writing a file. The scheduling aspect means it triggers future executions autonomously.
From the tool's definition 定时生成 Excel 报表 (Schedule/timed generation of Excel reports)
Attacks that exploit this kind of access
定时生成 Excel 报表. It is categorised as a Execute tool in the Office MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Office MCP Server MCP server in PolicyLayer and add a rule for schedule_excel_report_generation: 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 MCP Server. Nothing to install.
schedule_excel_report_generation 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 schedule_excel_report_generation 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 schedule_excel_report_generation. 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.
schedule_excel_report_generation is provided by the Office MCP Server MCP server (walkingzzzy/office-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →