指定されたデータベースのセッションが有効かどうかを確認します。
AI agents call fm_validate_session 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.
Session validation is a query operation that retrieves session state information. It has no side effects—it does not modify data, execute commands, delete records, or trigger financial transactions. The tool checks a boolean condition (valid/invalid) and returns the result. This is consistent with the 'Read' category for operations that retrieve or query data without side effects.
From the tool's definition Tool description states it 'confirms whether a session is valid' (validates session status). This is a status-check operation with no data modification, creation, deletion, or execution of external operations.
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_validate_session: 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_validate_session 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_validate_session 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_validate_session. 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_validate_session 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 →