// MCP TOOL REFERENCE

GRIDLY TOOLS

22 tools from the Gridly MCP Server, categorised by risk level.

READ TOOLS

get_record_history Get record histories of a record in a view list_databases List databases of a project list_dependencies List dependencies list_projects List grids of a database list_records List records in a view retrieve_column Retrieve a column retrieve_database Retrieve a database retrieve_dependency Retrieve a dependency retrieve_grid List grids of a database retrieve_project Retrieve a project retrieve_view Retrieve an existing view

WRITE TOOLS

add_column_to_view Add an existing grid column to a view 2/5 add_records Add new records to a view 2/5 create_column Create a column 2/5 create_grid Create a grid 2/5 create_view Create a collaborative view 2/5 update_grid Update a grid from a database 2/5

DESTRUCTIVE TOOLS

delete_column Delete a column 4/5 delete_dependency Delete a dependency 4/5 delete_grid Delete a grid 4/5 delete_records Delete existing records of a view 4/5 remove_column_from_view Remove a column from a view 4/5

// FAQ

How many tools does the Gridly MCP server have? +

The Gridly MCP server exposes 22 tools across 3 categories: Read, Write, Destructive.

How do I enforce policies on Gridly tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Gridly server.

What risk categories do Gridly tools fall into? +

Gridly tools are categorised as Read (11), Write (6), Destructive (5). Each category has a recommended default policy.

Enforce policies on Gridly

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →