get_agent_performance
Get detailed performance stats for a specific agent: run count, quality scores, approval/denial rates, error count, recent errors with context, and slowest runs. Use this to audit agent health, trace problems, and identify improvement opportunities.
This record as markdown: /tools/com-getfreedomos-freedom-mcp/get-agent-performance.md
What get_agent_performance does on Freedom Mcp
AI agents call get_agent_performance to retrieve information from Freedom Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
days | number | — | Lookback window in days (default: 30) |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
agent_name | string | Yes | Name of the agent to audit |
Parameters from the server's own tool schema.
Why get_agent_performance is rated Low
This tool queries and returns historical performance data about agents. It has no side effects, does not modify data, does not execute code or commands, and does not trigger financial or destructive operations. It is purely informational retrieval suitable for monitoring and diagnostics, placing it squarely in the Read category with low severity and high confidence.
From the tool's definition Tool retrieves 'detailed performance stats', 'run count', 'quality scores', 'approval/denial rates', 'error count', 'recent errors', and 'slowest runs' — all read operations with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs get_agent_performance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freedom Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_agent_performance, this is the rule to start with:
get_agent_performance 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 Freedom Mcp, apply this rule, and every get_agent_performance call is checked against it from then on.
Questions about get_agent_performance
Get detailed performance stats for a specific agent: run count, quality scores, approval/denial rates, error count, recent errors with context, and slowest runs. Use this to audit agent health, trace problems, and identify improvement opportunities. It is categorised as a Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.
get_agent_performance accepts 3 parameters: days, companyId, agent_name. Required: companyId, agent_name. The full parameter table on this page comes from the server's own tool schema.
Register the Freedom MCP server in PolicyLayer and add a rule for get_agent_performance: 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 Freedom Mcp. Nothing to install.
get_agent_performance 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 get_agent_performance 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 get_agent_performance. 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.
get_agent_performance is provided by the Freedom MCP server (https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freedom, and thousands of servers like it.
This server
Across the catalogue