fm_assert_record

THE RISK

Low Risk

Why fm_assert_record needs a policy

fm_assert_record performs a read-only comparison of existing record data against expected values. It retrieves data and validates it but produces no side effects—no creation, modification, deletion, or execution. The tool is clearly designed for testing/verification purposes.

From the tool's definition Tool description states 'Validates that a FileMaker record contains the expected field values. Returns PASS/FAIL with diff.' This is a validation/assertion operation that queries and compares data without modifying it.

Documented attack patterns abuse exactly the kind of access fm_assert_record gives an agent:

POLICY

How to control fm_assert_record

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "fm_assert_record": {}
  }
}

fm_assert_record is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Filemaker — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Filemaker 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 fie 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 Write fm_add_field Add a new field to an existing FileMaker table. SQL-style field types: VARCHAR(n), INT, NU 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).

All 19 Filemaker tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about fm_assert_record

What does the fm_assert_record tool do? +

Validates that a FileMaker record contains the expected field values. Returns PASS/FAIL with diff. It is categorised as a Read tool in the Filemaker MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fm_assert_record? +

Register the Filemaker MCP server in PolicyLayer and add a rule for fm_assert_record: 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 Filemaker. Nothing to install.

What risk level is fm_assert_record? +

fm_assert_record is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit fm_assert_record? +

Yes. Add a rate_limit block to the fm_assert_record 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.

How do I block fm_assert_record completely? +

Set action: deny in the PolicyLayer policy for fm_assert_record. 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.

What MCP server provides fm_assert_record? +

fm_assert_record is provided by the Filemaker MCP server (joergkoester/mcp-server-filemaker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

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 →