set_column_width · Fusebase MCP Server MCP: Risk & Policy

WHAT IT DOES

What set_column_width does on Fusebase MCP Server

AI agents use set_column_width to create or update resources in Fusebase MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fusebase MCP Server environment.

WHY IT NEEDS A POLICY

Why set_column_width needs a policy

This tool modifies a database view's presentation layer by changing column width. While not destructive or dangerous, it is a Write operation as it alters configuration/layout state. It poses medium severity because unintended width changes could disrupt UI layout or usability, but the changes are easily reversible.

From the tool's definition set_column_width modifies the display properties (column width in pixels) of a database view. The description explicitly states it 'Set[s] the width of a column', which is a modification operation that persists state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_column_width Rate-limited

set_column_width 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_column_width": {
      "limits": [
        {
          "counter": "set_column_width_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Fusebase MCP Server, so you can run agents against it safely.

FAQ

Questions about set_column_width

What does the set_column_width tool do? +

Set the width of a column in a database view. Use get_database_schema first to find column keys. Width is in pixels. It is categorised as a Write tool in the Fusebase MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_column_width? +

Register the Fusebase MCP Server MCP server in PolicyLayer and add a rule for set_column_width: 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 Fusebase MCP Server. Nothing to install.

What risk level is set_column_width? +

set_column_width is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_column_width? +

Yes. Add a rate_limit block to the set_column_width 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.

How do I block set_column_width completely? +

Set action: deny in the PolicyLayer policy for set_column_width. 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.

What MCP server provides set_column_width? +

set_column_width is provided by the Fusebase MCP Server MCP server (ryan-haver/fusebase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.