fm_delete_record

THE RISK

Critical Risk

Why fm_delete_record needs a policy

This tool permanently removes records from a FileMaker database with no undo capability. Deletion is irreversible and represents data loss. While the blast radius is constrained by requiring a valid ROWID (reducing critical severity), unauthorized or mistaken deletion of production records poses significant operational risk. Destructive is the most severe applicable category.

From the tool's definition Tool name 'fm_delete_record' combined with description 'Delete a FileMaker record by ROWID' explicitly performs irreversible deletion of data.

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

POLICY

How to control fm_delete_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_delete_record:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "fm_delete_record"
  ]
}

fm_delete_record disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

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.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Filemaker tools

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). Write fm_create_test_record Creates a test record with a test tag. tagField must be an existing text field in the FM t

All 19 Filemaker tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Filemaker → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about fm_delete_record

What does the fm_delete_record tool do? +

Delete a FileMaker record by ROWID. It is categorised as a Destructive tool in the Filemaker MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on fm_delete_record? +

Register the Filemaker MCP server in PolicyLayer and add a rule for fm_delete_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_delete_record? +

fm_delete_record is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit fm_delete_record? +

Yes. Add a rate_limit block to the fm_delete_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_delete_record completely? +

Set action: deny in the PolicyLayer policy for fm_delete_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_delete_record? +

fm_delete_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 →