AI agents call list_user_activity to retrieve information from Edstem without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries user activity data with no side effects. It fits the 'Read' category as it merely fetches information about a user without modifying, executing, or deleting anything. The blast radius is low—misuse could expose user activity information but cannot alter system state or cause financial harm.
From the tool's definition Tool name 'list_user_activity' and description 'List a user' indicate a retrieval operation. Sibling tools like 'list_threads', 'list_users', and 'get_user' confirm this server's pattern of using 'list' and 'get' for read-only queries.
Attacks that exploit this kind of access
List a user. It is categorised as a Read tool in the Edstem MCP Server, which means it retrieves data without modifying state.
Register the Edstem MCP server in PolicyLayer and add a rule for list_user_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 Edstem. Nothing to install.
list_user_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 list_user_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 list_user_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.
list_user_activity is provided by the Edstem MCP server (rob-9/edstem-mcp). 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 →