AI agents use excel_close to create or update resources in WinScript — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WinScript environment.
Closing Excel can cause unsaved data loss if not coordinated with 'excel_save', but the action itself is reversible (the file persists, the application can be reopened). This is Write-category because it modifies application state reversibly.
From the tool's definition Tool name 'excel_close' and server context indicate closure of an Excel application instance, which modifies application state.
Documented attack patterns abuse exactly the kind of access excel_close gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WinScript, and nothing reaches the server without passing your rules. This is the rule we recommend for excel_close:
{
"version": "1",
"default": "deny",
"tools": {
"excel_close": {
"limits": [
{
"counter": "excel_close_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}excel_close 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_close. It is categorised as a Write tool in the WinScript MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WinScript MCP server in PolicyLayer and add a rule for excel_close: 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 WinScript. Nothing to install.
excel_close 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 excel_close 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 excel_close. 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.
excel_close is provided by the WinScript MCP server (ravaniroshan/winscript-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WinScript, 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.
17 WinScript tools catalogued and risk-classified — across an index of 43,000+ MCP servers.