指定されたレイアウトの総レコード数を取得します。レコードデータは取得せず、カウントのみを効率的に返します。
AI agents call fm_get_record_count to retrieve information from FileMaker MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a metadata retrieval operation (counting records) with no side effects, no data modification, and no ability to execute code or trigger external operations. It is a simple query that returns aggregate information. The minimal blast radius if misused (disclosing record count) and read-only nature place it in the Read category with low severity.
From the tool's definition Tool name 'fm_get_record_count' and description state it retrieves only a count of records without fetching actual record data. The server is explicitly described as 'read-only access' to FileMaker databases.
Attacks that exploit this kind of access
指定されたレイアウトの総レコード数を取得します。レコードデータは取得せず、カウントのみを効率的に返します。. It is categorised as a Read tool in the FileMaker MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FileMaker MCP Server MCP server in PolicyLayer and add a rule for fm_get_record_count: 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 MCP Server. Nothing to install.
fm_get_record_count 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_record_count 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_record_count. 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_record_count is provided by the FileMaker MCP Server MCP server (ta-toshio/filemaker-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →