AI agents call reelgrep_list_searches to retrieve information from Reelgrep without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves metadata about past searches without modifying any underlying data. It is a retrieval operation with no side effects, fitting squarely into the Read category. The severity is low because the blast radius of misuse (viewing search history) is minimal and causes no damage to the video library or system.
From the tool's definition Tool name and description indicate listing/retrieving historical search data: 'List person/object searches that have been run against the library'. No modification, deletion, or execution is indicated.
Attacks that exploit this kind of access
List person/object searches that have been run against the library, newest first. Optionally scope to one video. It is categorised as a Read tool in the Reelgrep MCP Server, which means it retrieves data without modifying state.
Register the Reelgrep MCP server in PolicyLayer and add a rule for reelgrep_list_searches: 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 Reelgrep. Nothing to install.
reelgrep_list_searches 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 reelgrep_list_searches 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 reelgrep_list_searches. 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.
reelgrep_list_searches is provided by the Reelgrep MCP server (solomonneas/reelgrep-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 →