Get recent activity of the current user (views, edits).
AI agents call superset_recent_activity to retrieve information from MCP Superset without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns historical activity data (views and edits) for the current user. It performs read-only retrieval with no capability to modify, delete, execute, or create resources. The scope is limited to the current user's own activity log, minimizing potential blast radius. Low severity due to informational nature and no destructive or external operation capability.
From the tool's definition Tool name contains 'recent_activity' and description states 'Get recent activity of the current user (views, edits)' — purely a retrieval operation with no data modification or side effects.
Documented attack patterns abuse exactly the kind of access superset_recent_activity gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Superset, and nothing reaches the server without passing your rules. This is the rule we recommend for superset_recent_activity:
{
"version": "1",
"default": "deny",
"tools": {
"superset_recent_activity": {}
}
}superset_recent_activity is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get recent activity of the current user (views, edits). It is categorised as a Read tool in the MCP Superset MCP Server, which means it retrieves data without modifying state.
Register the MCP Superset MCP server in PolicyLayer and add a rule for superset_recent_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 MCP Superset. Nothing to install.
superset_recent_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 superset_recent_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 superset_recent_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.
superset_recent_activity is provided by the MCP Superset MCP server (mcp-superset). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Superset, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
137 MCP Superset tools catalogued and risk-classified — across an index of 43,000+ MCP servers.