get_info
Get full details for a video including transcript and chapters.
This record as markdown: /tools/0xchamin-mcptube/get-info.md
What get_info does on Mcptube Vision
AI agents call get_info to retrieve information from Mcptube Vision without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_info is rated Low
This tool retrieves and queries video metadata, transcripts, and structural information. It performs no mutations, deletions, code execution, or external operations—purely informational access. The severity is low because retrieving video details poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'get_info' and description 'Get full details for a video including transcript and chapters' indicate retrieval of existing data with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcptube Vision, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_info, this is the rule to start with:
get_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcptube Vision, apply this rule, and every get_info call is checked against it from then on.
Questions about get_info
Get full details for a video including transcript and chapters. It is categorised as a Read tool in the Mcptube Vision MCP Server, which means it retrieves data without modifying state.
Register the Mcptube Vision MCP server in PolicyLayer and add a rule for get_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 Mcptube Vision. Nothing to install.
get_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 get_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 get_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.
get_info is provided by the Mcptube Vision MCP server (0xchamin/mcptube). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcptube Vision, and thousands of servers like it.
This server
Across the catalogue