Browse the TikVid video feed. Returns videos with descriptions, likes, comments.
AI agents call browse_feed to retrieve information from TikVid MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays existing video feed data without creating, modifying, deleting, or executing any operations. It has no side effects and poses minimal security risk if misused by an AI agent, as it only exposes publicly available feed information.
From the tool's definition Tool name is 'browse_feed' and description states it 'Returns videos with descriptions, likes, comments' — a pure data retrieval operation with no modification, deletion, or execution of external actions.
Attacks that exploit this kind of access
Browse the TikVid video feed. Returns videos with descriptions, likes, comments. It is categorised as a Read tool in the TikVid MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TikVid MCP Server MCP server in PolicyLayer and add a rule for browse_feed: 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 TikVid MCP Server. Nothing to install.
browse_feed 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 browse_feed 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 browse_feed. 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.
browse_feed is provided by the TikVid MCP Server MCP server (liortesta/tikvid). 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 →