agent_activity
Get recent activity log for an agent (chat, tool calls, file uploads, etc.).
This record as markdown: /tools/io-github-proagentstore-platform/agent-activity.md
What agent_activity does on ProAgentStore
AI agents call agent_activity to retrieve information from ProAgentStore without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why agent_activity is rated Low
This tool retrieves and queries an activity log—a read-only operation that returns historical information about agent behavior. There is no creation, modification, deletion, code execution, or financial impact. The natural language 'Get' and 'activity log' confirm a passive data retrieval function.
From the tool's definition Tool name 'agent_activity' and description 'Get recent activity log' indicate retrieval of historical data with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs agent_activity safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ProAgentStore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For agent_activity, this is the rule to start with:
agent_activity is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ProAgentStore, apply this rule, and every agent_activity call is checked against it from then on.
Questions about agent_activity
Get recent activity log for an agent (chat, tool calls, file uploads, etc.). It is categorised as a Read tool in the ProAgentStore MCP Server, which means it retrieves data without modifying state.
Register the ProAgentStore MCP server in PolicyLayer and add a rule for agent_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 ProAgentStore. Nothing to install.
agent_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 agent_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 agent_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.
agent_activity is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ProAgentStore, and thousands of servers like it.
This server
Across the catalogue