映画の在庫・貸出状況を確認します。
AI agents call check_film_availability to retrieve information from Sakila MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a read-only query to check availability and rental status of films. It retrieves data about inventory and checkout state without creating, modifying, or destructively altering any records. This aligns with the Read category pattern (get, fetch, check) used consistently across sibling tools like get_film_details and get_customer_rentals.
From the tool's definition Tool description indicates it 'checks movie inventory/rental status' (映画の在庫・貸出状況を確認します). This is a query operation that retrieves current state of film availability without modifying, deleting, or executing external actions.
Attacks that exploit this kind of access
映画の在庫・貸出状況を確認します。. It is categorised as a Read tool in the Sakila MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sakila MCP Server MCP server in PolicyLayer and add a rule for check_film_availability: 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 Sakila MCP Server. Nothing to install.
check_film_availability 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 check_film_availability 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 check_film_availability. 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.
check_film_availability is provided by the Sakila MCP Server MCP server (mo3g4u/mcp-server-sample). 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 →