View your own activity log — all actions you have taken on TikVid with timestamps.
AI agents call get_my_activity 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 personal activity history. It queries existing data (activity log) without creating, modifying, deleting, or executing any operations. The action is purely observational. Even if an AI agent misuses this tool, it can only view data the user has already generated, posing minimal risk.
From the tool's definition Tool name 'get_my_activity' and description 'View your own activity log — all actions you have taken on TikVid with timestamps' indicate retrieval of historical data with no modification or side effects.
Attacks that exploit this kind of access
View your own activity log — all actions you have taken on TikVid with timestamps. 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 get_my_activity: 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.
get_my_activity 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_my_activity 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_my_activity. 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_my_activity 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 →