This record as markdown: /tools/frontmcp/activities-stats.md
What activities-stats does on Frontmcp
AI agents call activities-stats to retrieve information from Frontmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why activities-stats is rated Low
This tool retrieves or aggregates activity statistics from an existing data source. The verb 'Get' and the noun 'statistics' (a computed summary of existing data) are characteristic of Read operations. No side effects, modifications, or deletions are described or implied. The context of sibling tools (activities-list, activities-log) reinforces this as a data retrieval tool within an activity tracking system.
From the tool's definition Tool name 'activities-stats' and description 'Get activity statistics' indicate a retrieval operation that queries and returns statistical data without modifying, deleting, or executing any operations.
Attacks that exploit this kind of access
The rule that runs activities-stats safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Frontmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For activities-stats, this is the rule to start with:
activities-stats 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 Frontmcp, apply this rule, and every activities-stats call is checked against it from then on.
Questions about activities-stats
Get activity statistics. It is categorised as a Read tool in the Frontmcp MCP Server, which means it retrieves data without modifying state.
Register the Front MCP server in PolicyLayer and add a rule for activities-stats: 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 Frontmcp. Nothing to install.
activities-stats 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 activities-stats 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 activities-stats. 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.
activities-stats is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Front, and thousands of servers like it.
This server
Across the catalogue