17 tools. 2 can modify or destroy data without limits.
2 write tools that can modify data. Rate limits recommended.
Last updated:
Community server · catalogue entry verified 04/07/2026
Running more than one server? Check your whole stack →
2 of FileMaker MCP Server's 17 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.
PolicyLayer is an MCP gateway — it sits between your AI agents and FileMaker MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:
{
"fm_analyze_portal_data": {
"limits": [
{
"counter": "fm_analyze_portal_data_per_minute",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
} Controls API costs and prevents retry loops from exhausting upstream rate limits.
Instant setup, no code required.
The FileMaker MCP Server server is primarily read-only with 15 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.
17 tools across 2 categories: Read, Write. 15 are read-only. 2 can modify, create, or delete data.
Register the FileMaker MCP Server 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.
Deterministic rules across all 17 FileMaker MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Instant setup, no code required.
17 FileMaker MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.