Find video period.
AI agents call tools_find_video_period to retrieve information from vidMagik-mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to analyze or query video metadata to determine duration or periodicity information. The verb 'find' combined with the minimal, non-action description suggests passive data retrieval rather than transformation, execution, or modification. No destructive, financial, or code-execution implications are evident.
From the tool's definition Tool name 'tools_find_video_period' and description 'Find video period' indicate a query/analysis operation that retrieves or identifies temporal properties of video content without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Find video period. It is categorised as a Read tool in the vidMagik-mcp MCP Server, which means it retrieves data without modifying state.
Register the vidMagik- MCP server in PolicyLayer and add a rule for tools_find_video_period: 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 vidMagik-mcp. Nothing to install.
tools_find_video_period 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 tools_find_video_period 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 tools_find_video_period. 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.
tools_find_video_period is provided by the vidMagik- MCP server (vizionik25/vidmagik-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 →