// MCP TOOL REFERENCE

FILEMAKER TOOLS

19 tools from the Filemaker MCP Server, categorised by risk level.

// ALL 19 FILEMAKER TOOLS

READ 8 tools

Read fm_batch Execute multiple OData GET requests in a single HTTP call (batch). Use individual tools for write operations. Read fm_assert_count Checks whether a query returns the expected number of records. Useful for validating script results. Read fm_assert_record Validates that a FileMaker record contains the expected field values. Returns PASS/FAIL with diff. Read fm_get_metadata Reads the full OData $metadata document of the FileMaker database (EDMX/XML). Contains all tables, fields, ... Read fm_get_record Read a single FileMaker record by ROWID. Read fm_get_service_document Lists all available EntitySets (tables/layouts) of the FileMaker database. Read fm_introspect Analyzes the database structure: lists tables or shows all fields of a table with native FM field types fro... Read fm_query Query records from a FileMaker table. Supports OData $filter, $select, $top, $skip, $orderby, $expand, $cou...

WRITE 6 tools

Write fm_add_field Add a new field to an existing FileMaker table. SQL-style field types: VARCHAR(n), INT, NUMERIC, DATE, TIME... Write fm_create_record Create a new record in a FileMaker table. Write fm_create_table Create a new table in the FileMaker database (schema modification via OData). Write fm_create_test_record Creates a test record with a test tag. tagField must be an existing text field in the FM table. Returns ROW... Write fm_set_globals Sets global fields via FileMaker Data API (not OData). Opens a Data API session, sets the globals, then clo... Write fm_update_record Update an existing FileMaker record by ROWID (PATCH).

DESTRUCTIVE 2 tools

Destructive fm_delete_record Delete a FileMaker record by ROWID. Destructive fm_cleanup_test_data Deletes all test records marked with a specific tag. tagField must be an existing text field in the FM table.

EXECUTE 3 tools

Execute fm_run_script Run a FileMaker script. Returns scriptResult with code and resultParameter. Execute fm_run_script_and_assert Runs a FileMaker script and checks whether the result code matches the expected value. Execute fm_run_script_with_globals Sets global fields and runs a script in the SAME Data API session. This makes scripts that depend on global...

// FAQ

How many tools does the Filemaker MCP server have? +

The Filemaker MCP server exposes 19 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on Filemaker tools? +

Route the Filemaker server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do Filemaker tools fall into? +

Filemaker tools are categorised as Read (8), Write (6), Destructive (2), Execute (3). Each category has a recommended default policy.

Enforce policy on every Filemaker tool call.

Start from Filemaker, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.