Return video metadata (fps, width, height, frame count, duration).
AI agents call video_info to retrieve information from farshid-mcp-imageProcessing without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and reports metadata about a video file. It performs no side effects, does not modify data, does not execute code or external operations, and does not delete anything. It is a pure read operation querying video properties.
From the tool's definition Tool returns video metadata (fps, width, height, frame count, duration) with no modification or execution capability. The verb 'Return' and the list of metadata-only outputs indicate a query/retrieval operation.
Attacks that exploit this kind of access
Return video metadata (fps, width, height, frame count, duration). It is categorised as a Read tool in the farshid-mcp-imageProcessing MCP Server, which means it retrieves data without modifying state.
Register the farshid-mcp-imageProcessing MCP server in PolicyLayer and add a rule for video_info: 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 farshid-mcp-imageProcessing. Nothing to install.
video_info 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 video_info 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 video_info. 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.
video_info is provided by the farshid-mcp-imageProcessing MCP server (pirahansiah/farshid-mcp-imageprocessing). 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 →