set_column_widths
设置列宽
This record as markdown: /tools/1126misakp-excel-mcp-server-with-supabase-storage/set-column-widths.md
What set_column_widths does on Excel MCP Server with Supabase Storage
AI agents use set_column_widths to create or update resources in Excel MCP Server with Supabase Storage, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Excel MCP Server with Supabase Storage environment.
Why set_column_widths is rated Medium
The tool modifies column width properties in an Excel file, which is a Write operation—it changes the document state but is easily reversible (widths can be reset). It does not create/delete data, execute code, or cause financial harm. Severity is low because formatting changes have minimal blast radius and do not affect data integrity or functionality.
From the tool's definition Tool name 'set_column_widths' and description '设置列宽' (set column widths in Chinese) indicate a formatting operation that modifies spreadsheet column dimensions. This is a reversible structural modification to the Excel document.
Attacks that exploit this kind of access
The rule that runs set_column_widths safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Excel MCP Server with Supabase Storage, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_column_widths, this is the rule to start with:
set_column_widths 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Excel MCP Server with Supabase Storage, apply this rule, and every set_column_widths call is checked against it from then on.
Questions about set_column_widths
设置列宽. It is categorised as a Write tool in the Excel MCP Server with Supabase Storage MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Excel MCP Server with Supabase Storage MCP server in PolicyLayer and add a rule for set_column_widths: 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 Excel MCP Server with Supabase Storage. Nothing to install.
set_column_widths 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 set_column_widths 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 set_column_widths. 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.
set_column_widths is provided by the Excel MCP Server with Supabase Storage MCP server (1126misakp/excel-mcp-server-with-supabase-storage). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Excel MCP Server with Supabase Storage, and thousands of servers like it.
Across the catalogue