Add a new row to a database entity table. For built-in entities (clients, spaces), only entity name is needed. For custom databases, also provide databaseId and dashboardId (from list_databases or create_database). Uses Next.js server action internally.
AI agents use add_database_row 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.
The tool creates new database rows, which is a reversible write operation. It does not execute arbitrary code, delete data irreversibly, move money, or retrieve data. The severity is medium because uncontrolled row insertion could enable data pollution, spam, or resource exhaustion in a workspace database, but the operation itself is not destructive or financially consequential.
From the tool's definition Tool description states 'Add a new row to a database entity table' and 'Uses Next.js server action internally.' This explicitly creates new data records that can be modified or deleted later.
Attacks that exploit this kind of access
Add a new row to a database entity table. For built-in entities (clients, spaces), only entity name is needed. For custom databases, also provide databaseId and dashboardId (from list_databases or create_database). Uses Next.js server action internally. 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.
Register the Fusebase MCP Server MCP server in PolicyLayer and add a rule for add_database_row: 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.
add_database_row 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 add_database_row 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 add_database_row. 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.
add_database_row 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.
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 →