// MCP TOOL REFERENCE

DEVTOOLS TOOLS

11 tools from the Devtools MCP Server, categorised by risk level.

READ TOOLS

get_active_queries Get all active live queries and their data get_auth_state Get the current authentication state get_events Get event history, optionally filtered by type get_state Get the full Spooky DevTools state (events, queries, auth, database) get_table_data Fetch all records from a database table list_connections List browser tabs connected to Spooky DevTools list_tables List all database tables

WRITE TOOLS

update_table_row Update a record in a database table

DESTRUCTIVE TOOLS

clear_history Clear the event history delete_table_row Delete a record from a database table

EXECUTE TOOLS

run_query Execute a SurrealQL query against the database

// FAQ

How many tools does the Devtools MCP server have? +

The Devtools MCP server exposes 11 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on Devtools 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 Devtools server.

What risk categories do Devtools tools fall into? +

Devtools tools are categorised as Read (7), Write (1), Destructive (2), Execute (1). Each category has a recommended default policy.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

GET STARTED →