Query records from a FileMaker table. Supports OData $filter, $select, $top, $skip, $orderby, $expand, $count. Default limit: 100 records (override with $top).
AI agents call fm_query to retrieve information from Filemaker without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
fm_query is a read-only data retrieval operation. It queries and returns FileMaker records using OData query parameters without creating, modifying, deleting, or executing any operations. The blast radius is limited to information disclosure; accidental or malicious use cannot corrupt, destroy, or alter data.
From the tool's definition Tool description states 'Query records from a FileMaker table' and supports OData filtering and selection operators. No modification, deletion, or execution of scripts is mentioned—only retrieval via $filter, $select, $top, $skip, $orderby, $expand, $count.
Documented attack patterns abuse exactly the kind of access fm_query 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_query:
{
"version": "1",
"default": "deny",
"tools": {
"fm_query": {}
}
}fm_query is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Query records from a FileMaker table. Supports OData $filter, $select, $top, $skip, $orderby, $expand, $count. Default limit: 100 records (override with $top). It is categorised as a Read tool in the Filemaker MCP Server, which means it retrieves data without modifying state.
Register the Filemaker MCP server in PolicyLayer and add a rule for fm_query: 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_query is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the fm_query 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_query. 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_query 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.