Low Risk

fm_get_service_document

Lists all available EntitySets (tables/layouts) of the FileMaker database.

How to control fm_get_service_document ↓

What fm_get_service_document does on Filemaker

AI agents call fm_get_service_document 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.

Low Risk

Why fm_get_service_document needs a policy

The tool performs a read-only query to discover available tables/layouts in the FileMaker database. It has no side effects, cannot modify data, and only returns informational schema metadata. While it could potentially reveal sensitive database structure information, the severity is low because it doesn't directly expose data contents or enable destructive actions.

From the tool's definition 'Lists all available EntitySets (tables/layouts)' - this is a schema introspection operation that retrieves metadata about database structure without modifying, executing code, or deleting data.

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

How to control fm_get_service_document

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_service_document:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "fm_get_service_document": {}
  }
}

fm_get_service_document is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Filemaker — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about fm_get_service_document

What does the fm_get_service_document tool do? +

Lists all available EntitySets (tables/layouts) of the FileMaker database. It is categorised as a Read tool in the Filemaker MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fm_get_service_document? +

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

fm_get_service_document is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit fm_get_service_document? +

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

Set action: deny in the PolicyLayer policy for fm_get_service_document. 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_get_service_document? +

fm_get_service_document 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.

Free to start. No card required.

19 Filemaker tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.