Search for actors, directors, or other film industry people by name.
AI agents call search_people to retrieve information from IMDB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only query operation that retrieves structured metadata about people in the film industry. It has no side effects, cannot execute code, modify data, delete data, or move money. The worst-case misuse scenario (e.g., enumeration of many people) has minimal blast radius since IMDB data is public and search operations are non-destructive.
From the tool's definition Tool description states 'Search for actors, directors, or other film industry people by name' - a search operation that retrieves public filmography and biographical data without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Search for actors, directors, or other film industry people by name. It is categorised as a Read tool in the IMDB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the IMDB MCP Server MCP server in PolicyLayer and add a rule for search_people: 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 IMDB MCP Server. Nothing to install.
search_people 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 search_people 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 search_people. 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.
search_people is provided by the IMDB MCP Server MCP server (ron103/imdb-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 →