FileMakerサーバーにログインしてセッションを確立します。aliasで対象データベースを指定します。認証情報は環境変数から取得されます。
AI agents invoke fm_login to trigger actions in FileMaker MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Logging in and establishing a session is an external operation with side effects (session creation, token issuance). It doesn't merely read data, but it also doesn't write, delete, or move money. 'Execute' best fits because it triggers an external operation (authentication handshake) whose effects depend on arguments (the alias/database target).
From the tool's definition "FileMakerサーバーにログインしてセッションを確立します" (Login to FileMaker server and establish a session). Triggers external authentication operation and creates a persistent session state.
Attacks that exploit this kind of access
FileMakerサーバーにログインしてセッションを確立します。aliasで対象データベースを指定します。認証情報は環境変数から取得されます。. It is categorised as a Execute tool in the FileMaker MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the FileMaker MCP Server MCP server in PolicyLayer and add a rule for fm_login: 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_login is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the fm_login 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_login. 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_login 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 →