Count how many movies match the criteria.
AI agents call count_movies to retrieve information from Movie Database 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 read-only aggregation query against the movie database. It retrieves a count of matching records based on search criteria but does not create, modify, delete, or execute any code. The blast radius of misuse is minimal—an agent could only query the database excessively (DoS risk) but cannot alter data or trigger external operations. This is a straightforward Read category tool with low severity.
From the tool's definition Tool name 'count_movies' and description 'Count how many movies match the criteria' indicate a query operation that retrieves aggregate data without modifying or executing operations.
Attacks that exploit this kind of access
Count how many movies match the criteria. It is categorised as a Read tool in the Movie Database MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Movie Database MCP Server MCP server in PolicyLayer and add a rule for count_movies: 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 Movie Database MCP Server. Nothing to install.
count_movies 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 count_movies 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 count_movies. 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.
count_movies is provided by the Movie Database MCP Server MCP server (patw/movie-mcp-simple). 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 →