create_dashboard_table · Fusebase MCP Server MCP

WHAT IT DOES

What create_dashboard_table does on Fusebase MCP Server

AI agents use create_dashboard_table 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 create_dashboard_table needs a policy

This tool creates/adds a new table view within a dashboard, which is a reversible write operation. It modifies the dashboard structure by adding a new view but does not delete, execute arbitrary operations, or move financial assets. The severity is medium because incorrect table creation could clutter dashboards or create confusion, but the impact is localized to the dashboard workspace and reversible.

From the tool's definition Tool creates a new table (tab) within an existing database dashboard, adding an additional table view. The verb 'create' and the action of 'adds an additional table view' indicate data structure modification that is reversible.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_dashboard_table Rate-limited

create_dashboard_table 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": {
    "create_dashboard_table": {
      "limits": [
        {
          "counter": "create_dashboard_table_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 create_dashboard_table

What does the create_dashboard_table tool do? +

Create a new table (tab) within an existing database dashboard. This adds an additional table view alongside the existing one. 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 create_dashboard_table? +

Register the Fusebase MCP Server MCP server in PolicyLayer and add a rule for create_dashboard_table: 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 create_dashboard_table? +

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

Can I rate-limit create_dashboard_table? +

Yes. Add a rate_limit block to the create_dashboard_table 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 create_dashboard_table completely? +

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

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