Get rows from a database view in a structured format optimised for agent use. Each row includes: rowUuid (needed for update_database_cell), cells (column name → value map), and rawCells (column key → value map). Also returns the schema (column name, key, type) so you can look up the correct colum...
AI agents call get_database_rows to retrieve information from Fusebase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries database rows and schema information without creating, modifying, or deleting any data. It is a straightforward read operation that returns structured data for agent use. The mention of returning rowUuid for use with update_database_cell does not change the nature of this tool — it only reads and provides metadata needed for other operations.
From the tool's definition Tool description states it 'Get rows from a database view in a structured format' and 'returns the schema' — purely retrieval operations with no modification, deletion, or side effects.
Attacks that exploit this kind of access
Get rows from a database view in a structured format optimised for agent use. Each row includes: rowUuid (needed for update_database_cell), cells (column name → value map), and rawCells (column key → value map). Also returns the schema (column name, key, type) so you can look up the correct column key before calling update_database_cell. Wraps get_database_data with friendly field names. It is categorised as a Read tool in the Fusebase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Fusebase MCP Server MCP server in PolicyLayer and add a rule for get_database_rows: 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.
get_database_rows is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_database_rows 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 get_database_rows. 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.
get_database_rows 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 →