query_location_time
AI agents call query_location_time to retrieve information from MCP Video Parser without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name and server context strongly suggest this retrieves or filters video data by location and time parameters without modifying or deleting content. It fits the 'Read' pattern of search/query operations. Lack of tool description creates minor uncertainty, but the naming convention and sibling tools provide sufficient evidence that this is a query/search operation.
From the tool's definition Tool name 'query_location_time' and sibling tools like 'search_videos', 'get_video_stats', and 'get_video_summary' indicate read-only querying patterns. Server description emphasizes 'query video content' and 'search videos by time, location'.
Attacks that exploit this kind of access
query_location_time. It is categorised as a Read tool in the MCP Video Parser MCP Server, which means it retrieves data without modifying state.
Register the MCP Video Parser MCP server in PolicyLayer and add a rule for query_location_time: 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 MCP Video Parser. Nothing to install.
query_location_time 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 query_location_time 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 query_location_time. 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.
query_location_time is provided by the MCP Video Parser MCP server (michaelbaker-dev/mcpvideoparser). 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 →