agent_analytics
Get usage analytics for an agent
This record as markdown: /tools/io-github-proagentstore-platform/agent-analytics.md
What agent_analytics does on ProAgentStore
AI agents call agent_analytics 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_analytics is rated Low
This tool retrieves and queries usage analytics data about an agent's performance or activity. It performs a read-only operation returning analytics information without creating, modifying, deleting, or executing any actions. The blast radius is minimal as it only exposes historical usage data.
From the tool's definition Tool name 'agent_analytics' and description 'Get usage analytics for an agent' indicate a data retrieval operation with no modification or execution capabilities.
Attacks that exploit this kind of access
The rule that runs agent_analytics 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_analytics, this is the rule to start with:
agent_analytics 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_analytics call is checked against it from then on.
Questions about agent_analytics
Get usage analytics for an agent. 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_analytics: 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_analytics 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_analytics 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_analytics. 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_analytics 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