list_activities
AI agents call list_activities to retrieve information from Jules MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The naming pattern 'list_activities' strongly suggests this tool retrieves or enumerates activities from a Jules coding session, similar to sibling tools like 'list_sessions' and 'list_sources' which are clearly Read operations. Although the description is empty and provides no direct evidence, the consistent naming convention and context of other Read-classified tools on this server support this classification.
From the tool's definition Tool name 'list_activities' indicates a listing/retrieval operation. The prefix 'list_' is characteristic of Read category operations that query data without side effects.
Attacks that exploit this kind of access
list_activities. It is categorised as a Read tool in the Jules MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Jules MCP Server MCP server in PolicyLayer and add a rule for list_activities: 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 Jules MCP Server. Nothing to install.
list_activities 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_activities 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_activities. 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_activities is provided by the Jules MCP Server MCP server (paladiamors/jules-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 →