Creates a test record with a test tag. tagField must be an existing text field in the FM table. Returns ROWID for later validation and cleanup.
AI agents use fm_create_test_record to create or update resources in Filemaker — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Filemaker environment.
This tool creates new records in the FileMaker database, which is a Write operation. While the data is tagged as test data and intended to be temporary/reversible (evidenced by the return of ROWID 'for later validation and cleanup'), the actual creation of database records is a Write-category action.
From the tool's definition Tool name 'fm_create_test_record' and description explicitly states it 'Creates a test record' — a reversible data creation operation. The tool is designed for test data setup with explicit cleanup capability ('cleanup' is mentioned in sibling tools).
Documented attack patterns abuse exactly the kind of access fm_create_test_record gives an agent:
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_create_test_record:
{
"version": "1",
"default": "deny",
"tools": {
"fm_create_test_record": {
"limits": [
{
"counter": "fm_create_test_record_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}fm_create_test_record stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Creates a test record with a test tag. tagField must be an existing text field in the FM table. Returns ROWID for later validation and cleanup. It is categorised as a Write tool in the Filemaker MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Filemaker MCP server in PolicyLayer and add a rule for fm_create_test_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.
fm_create_test_record is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the fm_create_test_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.
Set action: deny in the PolicyLayer policy for fm_create_test_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.
fm_create_test_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.
Start from Filemaker, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
19 Filemaker tools catalogued and risk-classified — across an index of 43,000+ MCP servers.