// SCAN REPORT

Filemaker

19 tools. 11 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 12 Jun 2026

11 can modify or destroy data

8 read-only

19 tools total

Community server · catalogue entry verified 12/06/2026

How to control Filemaker ↓

TOOL MAP

What Filemaker exposes to your agents

Read (8) Write / Execute (9) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Filemaker tools

Destructive · High fm_delete_record This tool permanently removes records from a FileMaker database with no undo capability. Destructive · High fm_cleanup_test_data This tool performs bulk deletion of records from a FileMaker database. Execute · High fm_run_script This tool executes code (FileMaker scripts) whose behavior and side effects are determined by the script argument. Execute · High fm_run_script_and_assert The tool executes FileMaker scripts whose effects depend entirely on script arguments and content.

11 of Filemaker's 19 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Filemaker

PolicyLayer is an MCP gateway — it sits between your AI agents and Filemaker, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "fm_delete_record": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "fm_add_field": {
    "limits": [
      {
        "counter": "fm_add_field_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "fm_batch": {
    "limits": [
      {
        "counter": "fm_batch_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Filemaker — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON FILEMAKER →

Free to start. No card required.

FULL CATALOGUE

All 19 Filemaker tools

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 fi

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, T 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 ROWID Write fm_set_globals Sets global fields via FileMaker Data API (not OData). Opens a Data API session, sets the globals, then closes Write fm_update_record Update an existing FileMaker record by ROWID (PATCH).

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, typ 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 from $ Read fm_query Query records from a FileMaker table. Supports OData $filter, $select, $top, $skip, $orderby, $expand, $count.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Filemaker

Can an AI agent delete data through the Filemaker MCP server? +

Yes. The Filemaker server exposes 2 destructive tools including fm_delete_record, fm_cleanup_test_data. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Filemaker? +

The Filemaker server has 6 write tools including fm_add_field, fm_create_record, fm_create_table. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Filemaker.

How many tools does the Filemaker MCP server expose? +

19 tools across 4 categories: Destructive, Execute, Read, Write. 8 are read-only. 11 can modify, create, or delete data.

How do I enforce a policy on Filemaker? +

Register the Filemaker MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Filemaker tool call.

Deterministic rules across all 19 Filemaker tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON FILEMAKER →

Free to start. No card required.

19 Filemaker tools catalogued and risk-classified — across an index of 43,000+ MCP servers.