Reads the full OData $metadata document of the FileMaker database (EDMX/XML). Contains all tables, fields, types, and relationships.
AI agents call fm_get_metadata 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.
This tool retrieves metadata about the database structure without side effects. It queries and returns schema information only, fitting the Read category definition of data retrieval with no side effects. Severity is low because metadata exposure alone does not directly enable data exfiltration or damage—it only reveals structural information that could inform further attacks but causes no immediate harm.
From the tool's definition Tool name includes 'get', description states 'Reads the full OData $metadata document' with no mention of modification, deletion, or execution. Returns schema information (tables, fields, types, relationships).
Documented attack patterns abuse exactly the kind of access fm_get_metadata 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_get_metadata:
{
"version": "1",
"default": "deny",
"tools": {
"fm_get_metadata": {}
}
} fm_get_metadata 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.
Reads the full OData $metadata document of the FileMaker database (EDMX/XML). Contains all tables, fields, types, and relationships. 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_get_metadata: 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_get_metadata 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_get_metadata 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_get_metadata. 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_get_metadata 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.